Loading...
Loading...
Found 40 Skills
Software development based on Extreme Programming (XP). Use it when implementing software features of any kind. Coordinates planning, TDD, refactoring, and commits.
Full-process specification for software development, covering requirements analysis, design, pre-development, development, testing, and delivery, including review mechanisms, coding specifications and Git workflow
End-to-end project engineering — from understanding user intent to architecture design, incremental build with verification, and systematic debugging. Covers scheduled tasks (cron jobs), dashboards, web apps, APIs, scripts, and any software the user wants built. Replaces coder + preview-dev with a unified methodology.
General software development best practices covering code quality, testing, security, performance, and maintainability across technology stacks
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
[Implementation] ⚡⚡⚡ Implement a feature [step by step]
Before adding abstraction, asks "do we need this now?" Activates when proposing factories, abstract classes, config-driven behavior, or "for future extensibility." Resists over-engineering. Three similar lines are better than a premature abstraction.
Used when executing implementation plans containing independent tasks in the current session
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
Integrate development-related requirement convergence, structured review, execution ruling and resumption closure into a fully automatically advancing workflow harness
Builds multi-layer features as vertical end-to-end slices instead of horizontal layers. Each slice is verified before the next begins. Use when: starting any task that spans 2+ layers (DB, API, UI, tests), building CRUD features, implementing multi-step flows, decomposing features into subtasks, or planning implementation order.
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.