the-startup

In the author's own words, from each skill's SKILL.md — showing the first 30 of 34 files.

• analyze

  Deep-research analysis of a codebase, a topic, or both. Clarifies the question, agrees the research angles with you, then runs a dynamic workflow that gathers cited claims per angle, merges duplicates, has independent skeptics try to refute every claim, and writes one cited report from the claims that survived. Use for "how does X work", "map the Y flow", "research Z", or any mechanism-level ques…

  plugins/start/skills/analyze/SKILL.md on GitHub (opens in a new tab)

• archive

  Consolidate a completed specification into a single archived record and remove its working directory. Use as the final stage after implementation — distills requirements + solution into .start/archive/[NNN]-[name].md and deletes the .start/specs/[NNN]-[name]/ directory.

  plugins/start/skills/archive/SKILL.md on GitHub (opens in a new tab)

• brainstorm

  Required first step before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.

  plugins/start/skills/brainstorm/SKILL.md on GitHub (opens in a new tab)

• constitution

  Create or update a project constitution with governance rules. Uses discovery-based approach to generate project-specific rules.

  plugins/start/skills/constitution/SKILL.md on GitHub (opens in a new tab)

• debug

  Systematically diagnose and resolve bugs through conversational investigation and root cause analysis

  plugins/start/skills/debug/SKILL.md on GitHub (opens in a new tab)

• document

  Generate and maintain documentation for code, APIs, and project components

  plugins/start/skills/document/SKILL.md on GitHub (opens in a new tab)

• implement

  Implementation entry point. Use to execute a completed specification. Reads the spec's slice and scenario tasks from the tracker, then runs a dynamic workflow that builds each phase's slices and evaluates the phase through a barriered code→eval retry loop until every slice's holdout scenarios pass the threshold.

  plugins/start/skills/implement/SKILL.md on GitHub (opens in a new tab)

• improve

  Find deepening opportunities in a codebase — refactors that turn shallow modules into deep ones for better testability and AI-navigability. Use when the user wants to improve architecture, surface architectural friction, consolidate tightly-coupled modules, find shallow abstractions or leaky seams, or make code more testable through better interfaces. Distinct from refactor (which executes behavi…

  plugins/start/skills/improve/SKILL.md on GitHub (opens in a new tab)

• refactor

  Refactor, simplify, or clean up code for improved maintainability without changing business logic

  plugins/start/skills/refactor/SKILL.md on GitHub (opens in a new tab)

• reflect

  Self-improvement from this project's Claude Code session logs. Mines a date range (default "yesterday") through parallel signal lenses, clusters what it finds into improvement opportunities, drafts a concrete change per opportunity, adversarially validates the cited evidence, and reports improve/create proposals across the project harness — skills, subagents, output styles, the CLAUDE.md/AGENTS.m…

  plugins/start/skills/reflect/SKILL.md on GitHub (opens in a new tab)

• review

  Evidence-based code review. Resolves the review scope (PR, branch, staged changes, paths, or a freeform description), detects the stack from project instructions and the changed files, picks the review dimensions and any installed specialist agents, confirms the plan with you, then runs the review as a dynamic workflow — parallel reviewers, duplicate consolidation, adversarial verification, and o…

  plugins/start/skills/review/SKILL.md on GitHub (opens in a new tab)

• specify-meta

  Scaffold, status-check, and manage specification directories. Use when creating a new spec, reading spec status, transitioning between phases, or logging decisions on a spec in .start/specs/.

  plugins/start/skills/specify-meta/SKILL.md on GitHub (opens in a new tab)

• specify-plan

  Author the implementation plan — the Plan part of spec.md (target state + phases) plus the implementation TASKS in the spec's tracker that /implement runs. Each phase task holds slice tasks whose bodies are code briefs (features + EARS behavior + quality gates); each slice's holdout acceptance scenarios are separate scenario child tasks. Use after requirements and solution.

  plugins/start/skills/specify-plan/SKILL.md on GitHub (opens in a new tab)

• specify-requirements

  Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on the Requirements part of a spec.md in .start/specs/.

  plugins/start/skills/specify-requirements/SKILL.md on GitHub (opens in a new tab)

• specify-solution

  Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on the Solution part of a spec.md in .start/specs/.

  plugins/start/skills/specify-solution/SKILL.md on GitHub (opens in a new tab)

• specify

  Create a comprehensive specification from a brief description. Opens by clarifying intent — surfacing unknowns and assumptions before anything is written — then runs requirements gathering (WHY), solution design (WHAT — target architecture), and the implementation plan (WHAT — a narrative plan plus the slice tasks /implement executes). The specification describes the target state and what "done"…

  plugins/start/skills/specify/SKILL.md on GitHub (opens in a new tab)

• test

  Use when completing implementation, fixing bugs, refactoring code, or any time you need to verify the test suite passes. Also use when tests fail and you hear "pre-existing" or "not my changes" — enforces strict code ownership. Ensures MECE coverage (no overlap, no gaps) and that ALL test categories including E2E are executed.

  plugins/start/skills/test/SKILL.md on GitHub (opens in a new tab)

• validate

  Validate in any of six modes — spec quality, single-file review, spec-to-implementation drift, constitution rule enforcement, comparison between two artifacts, or sanity-checking your understanding. Use when checking a spec by ID, validating a file by path, detecting drift, enforcing constitution rules, comparing two sources ("$X against $Y"), or asking a freeform validation question.

  plugins/start/skills/validate/SKILL.md on GitHub (opens in a new tab)

• feature-prioritization

  RICE, MoSCoW, Kano, and value-effort prioritization frameworks with scoring methodologies and decision documentation. Use when prioritizing features, evaluating competing initiatives, creating roadmaps, or making build vs defer decisions.

  plugins/team/skills/cross-cutting/feature-prioritization/SKILL.md on GitHub (opens in a new tab)

• pattern-detection

  Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices.

  plugins/team/skills/cross-cutting/pattern-detection/SKILL.md on GitHub (opens in a new tab)

• project-discovery

  Unified codebase discovery across structure navigation, tech-stack detection, and documentation extraction. Use when onboarding to a project, locating implementation paths, identifying frameworks/tooling, or validating docs against code reality.

  plugins/team/skills/cross-cutting/project-discovery/SKILL.md on GitHub (opens in a new tab)

• requirements-elicitation

  Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation. Use when clarifying vague requirements, resolving conflicting needs, documenting specifications, or validating requirements with stakeholders.

  plugins/team/skills/cross-cutting/requirements-elicitation/SKILL.md on GitHub (opens in a new tab)

• user-research

  User research and insight synthesis for interviews, usability testing, personas, journey mapping, and actionable product/design recommendations. Use when planning studies, collecting evidence, synthesizing patterns, or converting findings into prioritized decisions.

  plugins/team/skills/design/user-research/SKILL.md on GitHub (opens in a new tab)

• agentic-patterns

  Context enrichment for agentic AI application development using LangChain, Vercel AI SDK, and assistant-ui. Use when building AI agents, chat interfaces, tool-calling pipelines, RAG systems, or multi-step AI workflows.

  plugins/team/skills/development/agentic-patterns/SKILL.md on GitHub (opens in a new tab)

• api-contract-design

  REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns. Use when designing APIs, reviewing API contracts, evaluating API technologies, or implementing API endpoints.

  plugins/team/skills/development/api-contract-design/SKILL.md on GitHub (opens in a new tab)

• architecture-selection

  System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria. Use when designing system architectures, evaluating patterns, or planning scalability.

  plugins/team/skills/development/architecture-selection/SKILL.md on GitHub (opens in a new tab)

• domain-modeling

  Unified domain and data modeling for business entities, invariants, schema design, aggregate boundaries, and evolution strategy. Use when designing business models, schema changes, bounded contexts, or consistency rules.

  plugins/team/skills/development/domain-modeling/SKILL.md on GitHub (opens in a new tab)

• frontend-patterns

  Context enrichment for frontend UI development using shadcn/ui and Tailwind CSS. Use when building component libraries, implementing UI designs, theming, or working with accessible React components.

  plugins/team/skills/development/frontend-patterns/SKILL.md on GitHub (opens in a new tab)

• technical-writing

  Create architectural decision records (ADRs), system documentation, API documentation, and operational runbooks. Use when capturing design decisions, documenting system architecture, creating API references, or writing operational procedures.

  plugins/team/skills/development/technical-writing/SKILL.md on GitHub (opens in a new tab)

• testing

  Writing effective tests and running them successfully. Covers layer-specific mocking rules, test design principles, debugging failures, and flaky test management. Use when writing tests, reviewing test quality, or debugging test failures.

  plugins/team/skills/development/testing/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 185k stars · 6 skills
• marketingskillsby coreyhaines31 Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. 58.7k stars · 30 skills
• elephant-goldfish-modelby google Open-source skills for designing and reviewing software with AI agents 12.4k stars · 7 skills
• claude-skillsby Jeffallan 67 Specialized Skills for Full-Stack Developers. Transform Claude Code into your expert pair programmer. 12.2k stars · 30 skills
• autoharnessby tigerless-labs Building the self-learning layer next-gen agents will ship with, learning skills from real work. 10.7k stars · 1 skill
• universal-modderby rehan-remade Point Claude at any game. Skills, tools and the fal MCP that let Claude Code mod almost any PC game you own: recon, reverse engineering, fa… 9.5k stars · 13 skills