implement
Skill214 starsChanged 31 days agoMITView on GitHub
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.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- revisit-studies/studytheir own version, first seen Nov 9, 2026
- dz114879/skillstheir own version, first seen Nov 8, 2026
- Dimon94/dveritytheir own version, first seen Nov 8, 2026
- Dimon94/skillstheir own version, first seen Nov 8, 2026
- The-Vibe-Company/quivrtheir own version, first seen Nov 8, 2026
- miklschmidt/archboardtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use setup-ts-deep-modules, ask-matt and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 43 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 91 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 50 projects that use this
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 88 projects that use this
ryotaroh180105Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 42 projects that use this
GoogleSkillto-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Also in 168 projects that use this
- +3 more from google
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- mattpocock/skills★ 309ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- foambubble/foam★ 17ksame name
- formbricks/formbricks★ 13ksame name
- ArcReel/ArcReel★ 6.3ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- fallow-rs/fallow★ 5.3ksame name
- withcoral/coral★ 4.9ksame name
- bestofjs/bestofjs★ 3.1ksame name
181 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .aidriven/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- debugSkill
- release-betaSkill
- release-checkSkill
- release-rollbackSkill
- release-stableSkill
- reviewSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 0 are common, 18 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 171 edited versions we read keep these.
18
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Before starting, load these files:
- Distinctive: line 38
Read relevant existing files
- Distinctive: line 48
Add comprehensive type hints
- Distinctive: line 61
Verify functionality in UI
- Distinctive: line 62
Check browser console for errors
- Distinctive: line 63
Check HA logs for warnings
- Distinctive: line 68
Document any issues encountered
- Distinctive: line 154
Use strict TypeScript mode
- Distinctive: line 164
Follow HA integration patterns
- Distinctive: line 202
Before marking task as complete:
- Distinctive: line 218
Missing async/await: - Always await async functions
- Distinctive: line 219
Wrong imports: - Use relative imports correctly
- Distinctive: line 220
Missing type hints: - All functions need types
- Distinctive: line 222
Not following patterns: - Check existing code first
- Very specific: line 223
Forgetting to build: - Run npm run build after changes
- Distinctive: line 224
Not testing: - Always test in real Home Assistant
- Distinctive: line 230
Check existing similar code
- Distinctive: line 232
Check Home Assistant documentation
- Distinctive: line 234
Ask for clarification on unclear requirements
“Common” is measured: kept by at least 6 in 10 of the 171 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
- .aidriven/memorybank.md - Project architecture
- .aidriven/rules/clean_code.md - Coding standards
- .aidriven/rules/homeassistant_integration.md - HA patterns
- 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/
- Match existing code style
- Add comprehensive type hints
- Include JSDoc/docstrings
4. Build and Validate (TypeScript)
npm run build
npm run type-check
npm run lint:check5. 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)
// 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)
// 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)
# 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)
# 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
anytypes 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
# TypeScript
npm run build
npm run type-check
npm run lint
# Manual testing in HA
# 1. Restart HA
# 2. Check logs
# 3. Verify functionalityFiles Organization
Frontend (TypeScript):
- src/views/ - View components
- src/cards/ - Card components
- src/chips/ - Chip components
- src/popups/ - Popup components
- src/helpers/ - Helper utilities
- src/linus-strategy.ts - Main strategy
Backend (Python):
- custom_components/linus_dashboard/ - Integration root
- custom_components/linus_dashboard/const.py - Constants
- custom_components/linus_dashboard/coordinator.py - Data coordinator
- 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
- Missing async/await - Always await async functions
- Wrong imports - Use relative imports correctly
- Missing type hints - All functions need types
- No error handling - Wrap risky operations in try/catch
- Not following patterns - Check existing code first
- Forgetting to build - Run
npm run buildafter changes - Not testing - Always test in real Home Assistant
When Stuck
- Check existing similar code
- Review .aidriven/memorybank.md
- Check Home Assistant documentation
- Review integration patterns
- Ask for clarification on unclear requirements
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

