all publishers

rsmdt

@rsmdt source repo

77 published skills

  1. ▌
    Specify Requirements 2 · rsmdt bundle
    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/.
    580 repo stars
  2. ▌
    Specify Solution 2 · rsmdt bundle
    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/.
    580 repo stars
  3. ▌
    Specify Meta 2 · rsmdt bundle
    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/.
    580 repo stars
  4. ▌
    Document · rsmdt bundle
    Generate and maintain documentation for code, APIs, and project components
    580 repo stars
  5. ▌
    Refactor · rsmdt bundle
    Refactor, simplify, or clean up code for improved maintainability without changing business logic
    580 repo stars
  6. ▌
    Implement · rsmdt bundle
    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.
    580 repo stars
  7. ▌
    Validate 2 · rsmdt bundle
    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.
    580 repo stars
  8. ▌
    Brainstorm 2 · rsmdt bundle
    Required first step before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
    580 repo stars
  9. ▌
    Constitution 2 · rsmdt bundle
    Create or update a project constitution with governance rules. Uses discovery-based approach to generate project-specific rules.
    580 repo stars
  10. ▌
    Specify 2 · rsmdt bundle
    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" looks like; /implement runs those slice tasks through a barriered code→eval loop.
    580 repo stars
  11. ▌
    Test · rsmdt bundle
    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.
    580 repo stars
  12. ▌
    Debug · rsmdt bundle
    Systematically diagnose and resolve bugs through conversational investigation and root cause analysis
    580 repo stars
  13. ▌
    Review · rsmdt
    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 one ranked report. Use when asked to review code, a PR, a branch, staged changes, or a directory.
    580 repo stars
  14. ▌
    Analyze 2 · rsmdt bundle
    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 question that must be evidence-backed.
    580 repo stars
  15. ▌
    Improve · rsmdt bundle
    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 behavior-preserving cleanup); improve decides what to deepen and how to shape the interface, then hands off.
    580 repo stars
  16. ▌
    Reflect · rsmdt bundle
    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.md instruction, and guardrails (permission rules, hooks). Advisory — it never edits an artifact; you decide what to apply.
    580 repo stars
  17. ▌
    Specify Plan · rsmdt bundle
    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.
    580 repo stars
  18. ▌
    Archive · rsmdt bundle
    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.
    580 repo stars
  19. ▌
    Security Assessment 2 · rsmdt bundle
    Vulnerability review, threat modeling, OWASP patterns, and secure coding assessment. Use when reviewing code security, designing secure systems, performing threat analysis, or validating security implementations.
    580 repo stars
  20. ▌
    Agentic Patterns 2 · rsmdt
    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.
    580 repo stars
  21. ▌
    Technical Writing 2 · rsmdt bundle
    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.
    580 repo stars
  22. ▌
    Pattern Detection 2 · rsmdt bundle
    Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices.
    580 repo stars
  23. ▌
    Project Discovery 2 · rsmdt bundle
    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.
    580 repo stars
  24. ▌
    API Contract Design 2 · rsmdt bundle
    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.
    580 repo stars
  25. ▌
    Architecture Selection 2 · rsmdt bundle
    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.
    580 repo stars
  26. ▌
    Platform Operations 2 · rsmdt bundle
    Unified platform operations guidance for CI/CD pipeline design, deployment strategies, observability, SLI/SLOs, and incident-ready rollouts. Use when building release workflows, production monitoring, or reliability controls.
    580 repo stars
  27. ▌
    Feature Prioritization 2 · rsmdt bundle
    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.
    580 repo stars
  28. ▌
    Requirements Elicitation 2 · rsmdt bundle
    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.
    580 repo stars
  29. ▌
    Specify Incremental 2 · rsmdt bundle
    Decompose a single-feature specification into a linear, phase-by-phase implementation plan. Use this for medium-complexity work — single feature, one or two components — where transparent human-in-the-loop phase review is preferred over factory automation.
    580 repo stars
  30. ▌
    User Research 2 · rsmdt bundle
    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.
    580 repo stars
  31. ▌
    Implement Incremental 2 · rsmdt bundle
    Linear phase-loop orchestrator for single-feature implementation plans. Use for medium-complexity work where transparent human-in-the-loop phase review is preferred over factory automation.
    580 repo stars
  32. ▌
    Code Quality Review 2 · rsmdt bundle
    Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
    580 repo stars
  33. ▌
    Specify Factory 2 · rsmdt bundle
    Decompose a multi-feature or multi-component specification into factory-consumable artifacts. Use this for high-complexity work — multiple features, three or more components, or parallel-eligible workstreams.
    580 repo stars
  34. ▌
    Implement Direct 2 · rsmdt bundle
    Lightweight implementation orchestrator for low-complexity work — fixes, refactors, doc changes, or single-AC features that do not warrant a phase plan or factory decomposition.
    580 repo stars
  35. ▌
    Implement Factory 2 · rsmdt bundle
    Factory loop orchestrator for multi-feature or multi-component implementation manifests. Use for high-complexity work with parallel-eligible workstreams and holdout-scenario evaluation.
    580 repo stars
  36. ▌
    Summarize 2 · rsmdt
    Summarize files and directories into a concise report.
    580 repo stars
  37. ▌
    Summarize · rsmdt
    Summarize files and directories into a concise report.
    580 repo stars
  38. ▌
    Domain Modeling · rsmdt bundle
    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.
    580 repo stars
  39. ▌
    Performance Analysis · rsmdt bundle
    Measurement approaches, profiling patterns, bottleneck identification, and optimization guidance. Use when diagnosing performance issues, establishing baselines, identifying bottlenecks, or planning for scale. Always measure before optimizing.
    580 repo stars
  40. ▌
    Frontend Patterns · rsmdt
    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.
    580 repo stars
  41. ▌
    Writing Skills · rsmdt bundle
    Use when creating new skills, editing existing skills, auditing skill quality, converting skills to markdown conventions, or verifying skills before deployment. Triggers include skill authoring requests, skill review needs, or "the skill doesn't work" complaints.
    580 repo stars
  42. ▌
    Testing · rsmdt bundle
    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.
    580 repo stars
  43. ▌
    Performance Analysis 2 · rsmdt bundle
    Measurement approaches, profiling patterns, bottleneck identification, and optimization guidance. Use when diagnosing performance issues, establishing baselines, identifying bottlenecks, or planning for scale. Always measure before optimizing.
    580 repo stars
  44. ▌
    Frontend Patterns 2 · rsmdt
    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.
    580 repo stars
  45. ▌
    Writing Skills 2 · rsmdt bundle
    Use when creating new skills, editing existing skills, auditing skill quality, converting skills to markdown conventions, or verifying skills before deployment. Triggers include skill authoring requests, skill review needs, or "the skill doesn't work" complaints.
    580 repo stars
  46. ▌
    Testing 2 · rsmdt bundle
    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.
    580 repo stars
  47. ▌
    Review 2 · rsmdt bundle
    Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)
    580 repo stars
  48. ▌
    Domain Modeling 2 · rsmdt bundle
    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.
    580 repo stars
  49. ▌
    Document 2 · rsmdt bundle
    Generate and maintain documentation for code, APIs, and project components
    580 repo stars
  50. ▌
    Refactor 2 · rsmdt bundle
    Refactor, simplify, or clean up code for improved maintainability without changing business logic
    580 repo stars
  51. ▌
    Implement 2 · rsmdt
    Implementation entry point. Use to execute a completed specification. Auto-detects the decomposition tier (Direct, Incremental, or Factory) from spec artifacts and dispatches to the matching execution sub-skill.
    580 repo stars
  52. ▌
    Test 2 · rsmdt bundle
    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.
    580 repo stars
  53. ▌
    Pattern Detection · rsmdt bundle
    Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices.
    580 repo stars
  54. ▌
    Project Discovery · rsmdt bundle
    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.
    580 repo stars
  55. ▌
    Specify Solution · rsmdt bundle
    Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution.md files in .start/specs/.
    580 repo stars
  56. ▌
    Specify Factory · rsmdt bundle
    Decompose a multi-feature or multi-component specification into factory-consumable artifacts. Use this for high-complexity work — multiple features, three or more components, or parallel-eligible workstreams.
    580 repo stars
  57. ▌
    Specify Meta · rsmdt bundle
    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/.
    580 repo stars
  58. ▌
    Constitution · rsmdt bundle
    Create or update a project constitution with governance rules. Uses discovery-based approach to generate project-specific rules.
    580 repo stars
  59. ▌
    Security Assessment · rsmdt bundle
    Vulnerability review, threat modeling, OWASP patterns, and secure coding assessment. Use when reviewing code security, designing secure systems, performing threat analysis, or validating security implementations.
    580 repo stars
  60. ▌
    Implement Incremental · rsmdt bundle
    Linear phase-loop orchestrator for single-feature implementation plans. Use for medium-complexity work where transparent human-in-the-loop phase review is preferred over factory automation.
    580 repo stars
  61. ▌
    Requirements Elicitation · rsmdt bundle
    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.
    580 repo stars
  62. ▌
    Architecture Selection · rsmdt bundle
    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.
    580 repo stars
  63. ▌
    Implement Factory · rsmdt bundle
    Factory loop orchestrator for multi-feature or multi-component implementation manifests. Use for high-complexity work with parallel-eligible workstreams and holdout-scenario evaluation.
    580 repo stars
  64. ▌
    Technical Writing · rsmdt bundle
    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.
    580 repo stars
  65. ▌
    Agentic Patterns · rsmdt
    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.
    580 repo stars
  66. ▌
    Implement Direct · rsmdt bundle
    Lightweight implementation orchestrator for low-complexity work — fixes, refactors, doc changes, or single-AC features that do not warrant a phase plan or factory decomposition.
    580 repo stars
  67. ▌
    Feature Prioritization · rsmdt bundle
    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.
    580 repo stars
  68. ▌
    Code Quality Review · rsmdt bundle
    Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
    580 repo stars
  69. ▌
    API Contract Design · rsmdt bundle
    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.
    580 repo stars
  70. ▌
    Platform Operations · rsmdt bundle
    Unified platform operations guidance for CI/CD pipeline design, deployment strategies, observability, SLI/SLOs, and incident-ready rollouts. Use when building release workflows, production monitoring, or reliability controls.
    580 repo stars
  71. ▌
    Specify Requirements · rsmdt bundle
    Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on requirements.md files in .start/specs/.
    580 repo stars
  72. ▌
    User Research · rsmdt bundle
    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.
    580 repo stars
  73. ▌
    Specify Incremental · rsmdt bundle
    Decompose a single-feature specification into a linear, phase-by-phase implementation plan. Use this for medium-complexity work — single feature, one or two components — where transparent human-in-the-loop phase review is preferred over factory automation.
    580 repo stars
  74. ▌
    Analyze · rsmdt bundle
    Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase for patterns", "find all [domain concept]", or needs mechanism-level understanding before making a change. Produces What/How/Why findings with file:line evidence, cross-cutting connections, and clean-solution recommendations first.
    580 repo stars
  75. ▌
    Validate · rsmdt bundle
    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.
    580 repo stars
  76. ▌
    Brainstorm · rsmdt
    You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
    580 repo stars
  77. ▌
    Specify · rsmdt bundle
    Create a comprehensive specification from a brief description. Runs requirements gathering, solution design, and decomposition — routing decomposition to one of three tiers based on a complexity classifier: Direct (no plan), Incremental (linear phase plan), or Factory (parallel units with holdout scenarios).
    580 repo stars