All authors
Claude Skills by rsmdt
github.com/rsmdt37 skills2 installs110 views
- Security AssessmentVulnerability review, OWASP patterns, secure coding practices, and threat modeling approaches. Use when reviewing code security, designing secure systems, performing threat analysis, or validating security implementations.Votes: 0GitHub stars: 511
- AnalyzeDeep-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 c...Votes: 0GitHub stars: 511
- BrainstormYou MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.Votes: 0GitHub stars: 511
- ConstitutionCreate or update a project constitution with governance rules. Uses discovery-based approach to generate project-specific rules.Votes: 0GitHub stars: 511
- DebugSystematically diagnose and resolve bugs through conversational investigation and root cause analysisVotes: 0GitHub stars: 511
- DocumentGenerate and maintain documentation for code, APIs, and project componentsVotes: 0GitHub stars: 511
- Implement DirectLightweight implementation orchestrator for low-complexity work — fixes, refactors, doc changes, or single-AC features that do not warrant a phase plan or factory decomposition.Votes: 0GitHub stars: 511
- Implement FactoryFactory loop orchestrator for multi-feature or multi-component implementation manifests. Use for high-complexity work with parallel-eligible workstreams and holdout-scenario evaluation.Votes: 0GitHub stars: 511
- Implement IncrementalLinear 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.Votes: 0GitHub stars: 511
- ImplementImplementation 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.Votes: 0GitHub stars: 511
- RefactorRefactor, simplify, or clean up code for improved maintainability without changing business logicVotes: 0GitHub stars: 511
- ReviewMulti-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)Votes: 0GitHub stars: 511
- Specify FactoryDecompose 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.Votes: 0GitHub stars: 511
- Specify IncrementalDecompose 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.Votes: 0GitHub stars: 511
- Specify MetaScaffold, 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/.Votes: 0GitHub stars: 511
- Specify RequirementsCreate 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/.Votes: 0GitHub stars: 511
- Specify SolutionCreate 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/.Votes: 0GitHub stars: 511
- SpecifyCreate 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).Votes: 0GitHub stars: 511
- TestUse 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.Votes: 0GitHub stars: 511
- ValidateValidate 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.Votes: 0GitHub stars: 511
- Writing SkillsUse 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.Votes: 0GitHub stars: 511
- ExamplesA complete skill demonstrating all gold-standard conventions, annotated with convention callouts. --- ```yaml --- name: review # kebab-case, matches skill directory name description: Multi-agent code review # trigger-focused, no workflow details with specialized perspectives user-invocable: true argument-hint: "PR number, branch # shown in / menu name, file path, or 'staged'" --- ```Votes: 0GitHub stars: 511
- Feature PrioritizationRICE, 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.Votes: 0GitHub stars: 511
- Pattern DetectionIdentify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices.Votes: 0GitHub stars: 511
- Project DiscoveryUnified 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.Votes: 0GitHub stars: 511
- Requirements ElicitationRequirement 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.Votes: 0GitHub stars: 511
- User ResearchUser 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.Votes: 0GitHub stars: 511
- Agentic PatternsContext 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.Votes: 0GitHub stars: 511
- Api Contract DesignREST 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.Votes: 0GitHub stars: 511
- Architecture SelectionSystem 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.Votes: 0GitHub stars: 511
- Domain ModelingUnified 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.Votes: 0GitHub stars: 511
- Frontend PatternsContext 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.Votes: 0GitHub stars: 511
- Technical WritingCreate 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.Votes: 0GitHub stars: 511
- TestingWriting 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.Votes: 0GitHub stars: 511
- Platform OperationsUnified 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.Votes: 0GitHub stars: 511
- Code Quality ReviewUnified 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.Votes: 0GitHub stars: 511
- Performance AnalysisMeasurement 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.Votes: 0GitHub stars: 511