All authors

Claude Skills by stevesolun
github.com/stevesolun71 skills0 installs149 views
- HandoffCompact the current conversation into a handoff document for another agent to pick up.Votes: 0GitHub stars: 583
- ImplementImplement work from a spec, ticket, or agreed conversation. Use explicitly when the user wants an existing plan carried through to working code.Votes: 0GitHub stars: 583
- Improve Codebase ArchitectureAnalyze a codebase for high-leverage architectural improvements and explain evidence, tradeoffs, and next steps. Use explicitly for architecture audits or deep-module refactoring opportunities.Votes: 0GitHub stars: 583
- PrototypeBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.Votes: 0GitHub stars: 583
- ResearchInvestigate questions using high-trust primary sources and traceable citations. Use when the user asks for research, current documentation or API facts, source verification, or evidence-backed comparison.Votes: 0GitHub stars: 583
- Resolving Merge ConflictsResolve an in-progress Git merge or rebase conflict while preserving the relevant intent of both sides. Use when conflict markers or an interrupted merge/rebase need investigation and resolution.Votes: 0GitHub stars: 583
- Setup Matt Pocock SkillsConfigure repository-local tracker, triage, and domain-document conventions needed by the Matt Pocock engineering skills.Votes: 0GitHub stars: 583
- TddApply test-driven development with small, behavior-focused feedback loops. Use when the user asks to build or fix something test-first, mentions red-green-refactor, or wants integration tests.Votes: 0GitHub stars: 583
- TeachTeach a skill or concept at the user's current level, optionally preserving a lightweight multi-session learning record.Votes: 0GitHub stars: 583
- To SpecSynthesize an implementation-ready spec from the current conversation and relevant repository context. Use explicitly when the user wants agreed work captured as a spec or PRD.Votes: 0GitHub stars: 583
- To TicketsBreak a plan, spec, or conversation into dependency-aware, independently verifiable tickets. Use explicitly when the user wants work sliced for local planning or an issue tracker.Votes: 0GitHub stars: 583
- TriageClassify and advance issues or external pull requests through the configured triage workflow. Use explicitly to inspect queues, evaluate an item, recommend a state, or apply an authorized transition.Votes: 0GitHub stars: 583
- WayfinderMap a large, unclear, multi-session effort as linked decisions, then advance the map until the route to the destination is clear.Votes: 0GitHub stars: 583
- Writing Great SkillsDesign or revise concise skills with clear triggers, proportional constraints, progressive disclosure, and realistic validation.Votes: 0GitHub stars: 583
- Ctx DispatchCoordinate nontrivial work in the ctx repository when a task has independent investigation, implementation, or test lanes; compute-heavy checks; or repetitive changes suited to scripts or codemods. Use for decomposition and concurrency decisions, not simple edits or questions.Votes: 0GitHub stars: 583
- Ctx VerifySelect proportional validation for changes or reviews in the ctx repository. Use before handing off material code, workflow, migration, documentation, security, packaging, or release changes; before a PR; or when asked whether a change is adequately tested. Do not use for pure questions with no changed artifact.Votes: 0GitHub stars: 583
- CavemanUltra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.Votes: 0GitHub stars: 583
- No MistakesValidate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.Votes: 0GitHub stars: 583
- ConvertedGenerate production-ready CRUD REST API endpoints with validation, auth, error handling, pagination, tests, and OpenAPI docs. Auto-triggers when asked to create API endpoints, REST resources, or backend CRUD operations.Votes: 0GitHub stars: 11
- OriginalGenerate a complete CRUD REST API with validation, error handling, auth middleware, tests, and OpenAPI docs. Use when asked to create API endpoints, REST resources, or backend CRUD operations.Votes: 0GitHub stars: 11
- Micro PipelineGated micro-skill pipeline system. Auto-triggers when building, generating, or creating any multi-step output (documents, code, presentations, reports). Enforces a Scope-Plan-Build-Check-Deliver pipeline where each step has a pass/fail gate. Use this whenever the output quality matters and the task has more than one component.Votes: 0GitHub stars: 11