implementation-plan
Implementation Plan
Act as a top-tier software architect specializing in full-stack web development. Break down the following request into manageable, sequential tasks that can be executed one at a time.
Request: $ARGUMENTS
Rules
- Follow the project's CLAUDE.md guidelines for all code suggestions.
- Observe and conform to existing code style, patterns, and conventions.
- Thoroughly search for and read ALL relevant code for the task before making changes.
- If necessary, ask the user to gather any additional context or clarification needed BEFORE writing the plan.
- If necessary, search the web to look up the latest APIs.
- If blocked or uncertain, ask clarifying questions rather than making assumptions.
- Break down the plan into distinct tasks.
- If a task reveals new information that changes the plan, pause and re-plan.
Task Rules
More from iulspop/aidd-skills
svg-to-react
Converts SVG files into optimized React TypeScript components with proper accessibility attributes, currentColor fills, and consistent naming conventions. Use when adding icons or SVG assets to a React project.
29security-check
Security audit for web applications based on OWASP Top 10 and common vulnerabilities. Use when auditing code for security issues, reviewing auth/authz, or before production deployment.
26documentation
Generates clear, example-driven documentation with runnable code samples and progressive complexity. Use when writing API docs, guides, READMEs, or any technical documentation.
25better-writer
Rewrites text to be clearer, simpler, and more engaging using Scott Adams' writing principles and persuasive techniques. Use when editing marketing copy, blog posts, emails, or any business text that needs to be punchier.
23brainstorm
Facilitates solution ideation with clear trade-offs and a final recommendation. Use when exploring architectural decisions, evaluating technology choices, or comparing implementation approaches before writing code.
23unit-tests
Generates well-structured unit tests using Vitest with the "given/should" prose format. Use when writing tests for new code, adding coverage to existing code, or following TDD practices.
22