Skip to content
Skills Library
Programming · Building & coding

implement

/implement

Implement approved plans with precision and quality for Linus Dashboard Home Assistant integration. Use when implementing features, executing approved plans, writing code following standards, or developing new functionality.

Licence
MIT
Last repository change
22.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Implement approved plans with precision and quality for Linus Dashboard Home Assistant integration. Use when implementing features, executing approved plans, writing code following standards, or developing new functionality.

Original author description

Implement approved plans with precision and quality for Linus Dashboard Home Assistant integration. Use when implementing features, executing approved plans, writing code following standards, or developing new functionality.

How it works

  1. Your Role
  2. Context to Load
  3. Implementation Process
  4. Common Patterns
  5. Quality Standards
  6. Files Organization
  7. Checklist for Each Task
  8. Common Mistakes to Avoid
  9. When Stuck
Original SKILL.md headings · 231 lines, 738 words
SKILL.md preview
---
name: implement
description: Implement approved plans with precision and quality for Linus Dashboard Home Assistant integration. Use when implementing features, executing approved plans, writing code following standards, or developing new functionality.
---

# Implement Approved Plans

Implement approved plans for Linus Dashboard, a Home Assistant custom integration with TypeScript frontend and Python backend.

---

## Your Role

You are a senior full-stack developer implementing features for Linus Dashboard. You have an APPROVED PLAN that breaks down the work into specific tasks. Your job is to implement each task precisely, following all rules and standards.

---

## Context to Load

Before starting, load these files:
1. [.aidriven/memorybank.md](.aidriven/memorybank.md) - Project architecture
2. [.aidriven/rules/clean_code.md](.aidriven/rules/clean_code.md) - Coding standards
3. [.aidriven/rules/homeassistant_integration.md](.aidriven/rules/homeassistant_integration.md) - HA patterns
4. The approved plan document

---

## Implementation Process

### For Each Task:

#### 1. Read the Task Description
- Understand what needs to be done
- Identify files to create/modify
- Note any dependencies

#### 2. Check Existing Code
- Read relevant existing files
- Understand current patterns
- Identify integration points

#### 3. Write Code

Follow standards:
- TypeScript/Python best practices
- Apply all rules from [.aidriven/rules/](.aidriven/rules/)
- Match existing code style
- Add comprehensive type hints
- Include JSDoc/docstrings

#### 4. Build and Validate (TypeScript)
```bash
npm run build
npm run type-check
npm run lint:check
```

#### 5. Test Manually
- For backend changes: Restart Home Assistant
- For frontend changes: Clear browser cache (Ctrl+Shift+R)
- Verify functionality in UI
- Check browser console for errors
- Check HA logs for warnings

#### 6. Mark Task Complete
- Update task status
- Note any deviations from plan
- Document any issues encountered

---

## Common Patterns

### Adding a New View (TypeScript)

```typescript
// src/views/XxxView.ts
import { AbstractView } from "./AbstractView";
import { XxxCard } from "../cards/XxxCard";

export class XxxView extends AbstractView {
  /**
   * Create the Xxx view
   */
  async render(): Promise<void> {
    // Implementation
  }
}
```

### Adding a New Card (TypeScript)

```typescript
// src/cards/XxxCard.ts
import { AbstractCard } from "./AbstractCard";

export class XxxCard extends AbstractCard {
  /**
   * Render the card
   */
  protected async renderContent(): Promise<HTMLElement> {
    // Implementation
  }
}
```

### Adding a New Service (Python)

```python
# custom_components/linus_dashboard/services.py
async def async_setup_services(hass: HomeAssistant) -> None:
    """Set up Linus Dashboard services."""

    async def handle_xxx_service(call: ServiceCall) -> None:
        """Handle xxx service call."""
        # Implementation

    hass.services.async_register(
        DOMAIN,
        "xxx_service",
        handle_xxx_service,
        schema=XXX_SERVICE_SCHEMA,
    )
```

### Adding a New Sensor (Python)

```python
# custom_components/linus_dashboard/sensor.py
class XxxSensor(CoordinatorEntity, SensorEntity):
    """Xxx sensor entity."""

    def __init__(
        self,
        coordinator: DataUpdateCoordinator,
        entry: ConfigEntry,
    ) -> None:
        """Initialize the sensor."""
        super().__init__(coordinator)
        self._entry = entry
        self._attr_unique_id = f"{entry.entry_id}_xxx"

    @property
    def native_value(self) -> StateType:
        """Return the state."""
        return self.coordinator.data.get("xxx")
```

---

## Quality Standards

### TypeScript Code
- Use strict TypeScript mode
- Proper type annotations
- JSDoc comments for public APIs
- No `any` types without justification
- Follow existing patterns

### Python Code
- Type hints on all functions
- Docstrings in Google style
- Async/await for I/O operations
- Follow HA integration patterns
- Proper error handling

### Testing
```bash
# TypeScript
npm run build
npm run type-check
npm run lint

# Manual testing in HA
# 1. Restart HA
# 2. Check logs
# 3. Verify functionality
```

---

## Files Organization

**Frontend (TypeScript):**
- [src/views/](src/views/) - View components
- [src/cards/](src/cards/) - Card components
- [src/chips/](src/chips/) - Chip components
- [src/popups/](src/popups/) - Popup components
- [src/helpers/](src/helpers/) - Helper utilities
- [src/linus-strategy.ts](src/linus-strategy.ts) - Main strategy

**Backend (Python):**
- [custom_components/linus_dashboard/](custom_components/linus_dashboard/) - Integration root
- [custom_components/linus_dashboard/const.py](custom_components/linus_dashboard/const.py) - Constants
- [custom_components/linus_dashboard/coordinator.py](custom_components/linus_dashboard/coordinator.py) - Data coordinator
- [custom_components/linus_dashboard/sensor.py](custom_components/linus_dashboard/sensor.py) - Sensor platform

---

## Checklist for Each Task

Before marking task as complete:
- [ ] Code written following standards
- [ ] Type hints/annotations added
- [ ] Documentation added (JSDoc/docstrings)
- [ ] Build passes (TypeScript)
- [ ] No linting errors
- [ ] Manually tested in Home Assistant
- [ ] No errors in browser console
- [ ] No errors in HA logs
- [ ] Code follows existing patterns
- [ ] Task notes updated

---

## Common Mistakes to Avoid

1. **Missing async/await** - Always await async functions
2. **Wrong imports** - Use relative imports correctly
3. **Missing type hints** - All functions need types
4. **No error handling** - Wrap risky operations in try/catch
5. **Not following patterns** - Check existing code first
6. **Forgetting to build** - Run `npm run build` after changes
7. **Not testing** - Always test in real Home Assistant

---

## When Stuck

1. Check existing similar code
2. Review [.aidriven/memorybank.md](.aidriven/memorybank.md)
3. Check Home Assistant documentation
4. Review integration patterns
5. Ask for clarification on unclear requirements

Versions

RepositoryScoreLicence
This page · Thank-you-Linus/Linus-Dashboard100MIT
ericrisco/rsc-harness100MIT
yonatangross/orchestkit100MIT
sentimony/agentic-workflow100MIT
moberghr/mtk-agent-toolkit100MIT
michielvandermeer/skills100MIT
rossumai/claude-marketplace100MIT
userKael/rastro100MIT
yonatangross/orchestkit100MIT

Database snapshot: 13.11.2026 · package version d5b768374f34 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95implementation
    Implement features with code, tests, and documentation. Use when building features from approved designs following TDD and project coding standards.
  • 90home-assistant-integration
    Keeps Home Assistant transport, raw entity state, mappers, actions, and React containers behind the dashboard's normalized card props. Use when adding or reviewing live Home Assistant integration, entity adapters, service actions, connection/store code, or dashboard containers.…
  • 100ha-integration-scaffold
    Scaffold a new Home Assistant integration with correct file structure, manifest, and boilerplate. Use when creating a new custom component, custom integration, or when asked to scaffold, create, or start a Home Assistant integration.
  • 100ha-diagnostics
    Implement diagnostics for a Home Assistant integration. Required for Gold tier on the Integration Quality Scale. Use when asked about diagnostics.py, debug information, troubleshooting data, or redacting sensitive info.
  • 10002-implement
    Implement features, refactors, or bug fixes strictly traceable to an approved specification or issue, enforcing stack-specific engineering standards, living spec synchronization, and automated test verification. Activate when implementing code, fixing bugs, or running /02-implement.
  • 100sdd-implementation
    Execute planned implementations following todo-lists systematically. Use for code generation, building features, and executing SDD plans.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.