Claude Skills by ilandahan

AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.

AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.

AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.

AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.

AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.

AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.

Build an Atomic Design system from Figma style guides - extract tokens, create atoms/molecules/organisms/templates/pages as reusable component libraries. Use when building or extending a design system or component library.

Build pages using ONLY existing atomic-design components. REQUIRES atomic-design skill. Use for composing pages, creating views/features from existing components.

Bounded improvement loop: one artifact, fixed eval score, keep an edit only if strictly better. Use for AR_DESIGN/AR_FUNCTION/AR_ACCEPTANCE stages or standalone bounded iteration.

Comprehensive code review for commits and pull requests. Covers security, TDD, code quality, and documentation standards.

Real-time work context tracking for session continuity. Maintains task/step state across sessions, tracks progress, manages logs, integrates with phase enforcement.

Cucumber BDD integration for AID methodology. Gherkin-first acceptance criteria with executable specifications. Use for writing feature files, step definitions, and running acceptance tests.

AI-powered design review for Figma components with weighted dual-scoring system. Evaluates Style Guide Implementation (70%) and LLM Metadata Accessibility (30%). For export, hands off to atomic-design skill.

Decision transparency, feedback collection, and debate invitations for AID methodology. Active in ALL phases for ALL roles.

AID Memory System for session feedback, learning cycles, and skill improvement. Manages state, feedback collection, and improvement analysis. Load for /aid-init, /aid-start, /aid-status, /aid-end, /aid-improve, /aid-memory, /aid-reset.

> **Source**: `../../commands/jira-breakdown.md` > > This file is a reference. The main prompt is in the `../../commands/` directory. > Use the `/jira-breakdown` command for work breakdown generation.

> **Source**: `../aid-development/SKILL.md` > > This file is a reference. The main skill definition is in the `.claude/skills/` directory.

> **Source**: `../pre-prd-research/SKILL.md`, `../aid-discovery/SKILL.md` > > This file is a quick reference. The main skill definitions are in the `.claude/skills/` directory.

> **Source**: `../aid-prd/SKILL.md` > > This file is a reference. The main skill definition is in the `.claude/skills/` directory. > Use the `/prd` command for PRD generation with the full 7-shot prompt.

> **Source**: `../aid-qa-ship/SKILL.md` > > This file is a reference. The main skill definition is in the `.claude/skills/` directory.

> **Source**: `../aid-tech-spec/SKILL.md` > > This file is a reference. The main skill definition is in the `.claude/skills/` directory. > Use the `/tech-spec` command for technical specification generation.

> **Source**: `../role-data-scientist/SKILL.md` > > This file is a reference. The main skill definition is in the `.claude/skills/` directory.

> **Source**: `../role-developer/SKILL.md` > > This file is a reference. The main skill definition is in the `.claude/skills/` directory.

> **Source**: `../role-product-manager/SKILL.md` > > This file is a reference. The main skill definition is in the `.claude/skills/` directory.

> **Source**: `../role-qa-engineer/SKILL.md` > > This file is a reference. The main skill definition is in the `.claude/skills/` directory.

> **Source**: `../role-tech-lead/SKILL.md` > > This file is a reference. The main skill definition is in the `.claude/skills/` directory.

[OPTIONAL] AI-powered visual generation using Google Nano Banana Pro. For user flows, architecture diagrams, mockups.

AID methodology phase gate enforcement. Ensures work follows correct 6-phase order (Discovery -> PRD -> Tech Spec -> Impl Plan -> Dev -> QA & Ship). Enforces gates, validates transitions. Use before any work to check the current phase and refuse work belonging to a later phase.

Drives the Phase 4-5 dev pipeline state machine with sub-agent reviews and bounded autoresearch gates. Use when running /pipeline or executing an approved plan.

Comprehensive code review for commits and pull requests. Covers security, TDD, code quality, and documentation standards.

TDD methodology for production-quality tests. Write tests FIRST driven by PRD, Tech Spec, Implementation Plan. Covers minimal mocking, realistic test data, strong assertions, test independence.

Pre-PRD Research methodology combining Business Analysis, Creative Problem-Solving, Brainstorming, and Innovation Strategy. Use before writing any PRD for problem validation, market research, competitive analysis, stakeholder interviews, ideation, root cause analysis.

Automatic quality check on significant outputs via isolated sub-agent. Spawns reflection-agent for objective evaluation without conversation context bias.

Data Scientist role within the AID methodology. Activate when working on: EDA, feasibility assessment, experiment planning, ML architecture, model development & validation, or production deployment & monitoring. Stack-agnostic — ask the user for their stack at the start of any new project.

Developer role in AID methodology. Use for implementation, debugging, technical design, TDD workflow, code review.

PM role in AID methodology. Use for requirements, user stories, acceptance criteria, stakeholder management, scope definition.

QA Engineer role in AID methodology. Use for test strategy, BDD scenarios, bug reporting, acceptance testing, flaky test prevention.

Tech Lead role in AID methodology. Use for architecture decisions, code reviews, technical direction, operational readiness, team guidance.

Senior System Architect for SaaS specifications. Security-first design with ISO 27001 compliance. Use for system architecture, tech specs, API design, technology choices, distributed systems, cloud infrastructure.

TDD methodology for production-quality tests. Write tests FIRST driven by PRD, Tech Spec, Implementation Plan. Covers minimal mocking, realistic test data, strong assertions, test independence.

FOUNDATIONAL SKILL - Analyze every prompt for underlying motivation using Golden Circle (WHY->HOW->WHAT). Runs BEFORE any other skill. No action without understanding WHY.