| name | implement-feature |
| description | Implements a requested Pixel Creator feature or behavior while respecting existing architecture, tests, documentation, and ADR contracts. Use for concrete implementation work after the relevant architecture has been understood. |
Implement Pixel Creator Feature
Procedure
- Understand the requested behavior and acceptance criteria.
- Inspect the relevant implementation.
- Inspect relevant tests.
- Inspect relevant documentation and ADRs.
- If architecture-sensitive, use the
inspect-architecture skill first.
- Identify the smallest correct implementation.
- Implement the change without unrelated refactoring.
- Add or update tests for the intended behavior.
- Run targeted tests.
- Run the broader test suite when appropriate.
- Inspect the final diff.
- Report the implementation and verification.
Rules
Preserve existing architectural contracts.
Do not introduce TypeScript.
Do not add unnecessary dependencies.
Do not introduce speculative abstractions.
Do not modify unrelated files.
Do not silently change public APIs.
Do not silently change identity semantics.
Do not use runtime error handling as an excuse to mutate user-authored component state.
Do not automatically disable components after errors.
If blocked
If the requested behavior conflicts with an existing architectural contract:
- Explain the conflict.
- Identify the relevant code/tests/ADR.
- Present the smallest viable options.
- Do not silently choose an architectural change.
Completion criteria
A feature is not considered complete until:
- implementation is present;
- relevant tests exist or have been updated;
- relevant tests pass;
- the diff has been inspected.
