All authors
Claude Skills by duc01226
github.com/duc01226204 skills0 installs256 views
- Graph Export[Code Intelligence] Use when exporting the code knowledge graph. --format={json|mermaid}.Votes: 0GitHub stars: 3
- Harness Setup[Quality] Use when a workflow step or the user asks for an agent quality harness: feedforward guides and feedback sensors.Votes: 0GitHub stars: 3
- Idea[Project Management] Use when a workflow step or the user asks for an idea to be captured: ideas, feature requests, concepts for refinement.Votes: 0GitHub stars: 3
- Integration Test[Testing] Use when a workflow step or the user asks for integration tests: generate them, --mode=review (one-pass 8-gate review) or --mode=verify (run with runner evidence; --fix-loop converges failures).Votes: 0GitHub stars: 3
- Investigate[Fix & Debug] Use when a workflow step or the user asks for how an existing feature works (read-only code-flow trace) or --mode=debug: a bug''s root cause (reproduce, trace end-to-start). --mode=explain. Plans or decisions: understand.Votes: 0GitHub stars: 3
- Knowledge Review[Research] Use when a workflow step or the user asks for a knowledge artifact review: completeness, citations, confidence accuracy, template compliance.Votes: 0GitHub stars: 3
- Knowledge Synthesis[Research] Use when a workflow step or the user asks for a research synthesis: findings into a structured report.Votes: 0GitHub stars: 3
- Learn[Utilities] Use when teaching Claude a lesson that persists across sessions, including an extra rule for one skill or task kind (routes to project-skill-protocol).Votes: 0GitHub stars: 3
- Linter Setup[Quality] Use when a workflow step or the user asks for code quality tooling: linters, formatters, static analysis, pre-commit hooks, CI gates.Votes: 0GitHub stars: 3
- Llm Council[Decision Support] Use when pressure-testing an irreversible, high-stakes decision with adversarial AI advisors.Votes: 0GitHub stars: 3
- Market Analysis[Research] Use when a workflow step or the user asks for a market landscape analysis: competitors, TAM/SAM/SOM, trends, SWOT, segments.Votes: 0GitHub stars: 3
- Package Upgrade[Code Quality] Use when analyzing package upgrades, outdated dependencies, npm/NuGet update plans or breaking changes.Votes: 0GitHub stars: 3
- Performance Review[Debugging] Use when a workflow step or the user asks for a performance review: slow queries, N+1, latency, memory, caching, frontend rendering, Web Vitals.Votes: 0GitHub stars: 3
- Plan[Planning] Use when a workflow step or the user asks for a concise implementation plan, or --mode=review (one review pass) / --mode=validate (critical-questions interview) / --mode=execute (code and test it) of a plan. --mode={ci|cro}.Votes: 0GitHub stars: 3
- Prioritize[Project Management] Use when a workflow step or the user asks for backlog prioritization: RICE, MoSCoW or Value-Effort ranking.Votes: 0GitHub stars: 3
- Product Roadmap[Planning] Use ONLY when the user explicitly requests a product roadmap, roadmap update or milestone selection: outcome milestones, MVP scope, non-goals, risks, evidence gates.Votes: 0GitHub stars: 3
- Production Readiness Review[Code Quality] Use when a workflow step or the user asks for a production readiness review of service-layer and API changes.Votes: 0GitHub stars: 3
- Project Config[Utilities] Use when syncing the project-config file (default docs/project-config.json) with the current workspace structure. Not reference docs (scan) or CLAUDE.md (ai-context-refresh).Votes: 0GitHub stars: 3
- Project Init[Utilities] Use when setting up or re-evaluating portable project context end to end: project-config, reference docs, CLAUDE.md, AGENTS.md. One piece only: project-config, docs-manager --mode=init or ai-context-refresh.Votes: 0GitHub stars: 3
- Project Skill Protocol[Utilities] Use when a project adds, changes, lists or removes its OWN protocol rules layered over a framework skill (additive only). list | add | update | delete.Votes: 0GitHub stars: 3
- Prompt Enhance[Skill Management] Use when enhancing, compressing or expanding prompts, docs or skills. --op={compress|expand|enhance}.Votes: 0GitHub stars: 3
- Release Doc[Git] Use when creating release notes or a release document from git history at any scope (tag, branch, time range), as markdown plus a standalone HTML presentation.Votes: 0GitHub stars: 3
- Remotion[User-Invoked] Use when creating, updating, or previewing Remotion videos.Votes: 0GitHub stars: 3
- Scaffold[Architecture] Use when a workflow step or the user asks for project scaffolding: foundations and golden-path examples before feature implementation.Votes: 0GitHub stars: 3
- Scan All[Documentation] Use when refreshing every selected, evidence-applicable reference-doc scan target at once. One doc: scan; first-time setup: docs-manager --mode=init.Votes: 0GitHub stars: 3
- Scan Codebase Health[Documentation] Use when detecting codebase health issues: unused exports, doc count-drift, orphan files, stale config references.Votes: 0GitHub stars: 3
- Scan[Documentation] Use when a workflow step or the user asks for one project-reference doc to be regenerated. --target=<doc key> (project-structure, code-review-rules, domain-entities, docs-index). All docs: scan-all.Votes: 0GitHub stars: 3
- Scenario[Planning] Use when a workflow step or the user asks for adversarial scenarios: failure modes, data integrity, state boundaries, access risks.Votes: 0GitHub stars: 3
- Seed Test Data[Dev Data] Use when a workflow step or the user asks for test-data seeders for QC happy paths. --mode=review audits a seeder read-only.Votes: 0GitHub stars: 3
- Skill Creator[Skill Management] Use when creating a skill, adding skill references or scripts, fixing invalid skill headers, or packaging skills.Votes: 0GitHub stars: 3
- Spec[Documentation] Use when a workflow step or the user asks for spec authoring, auditing, amending, test-speccing, reconciling, or [mode=discovery|clarify|index]: pre-spec landscape, user-confirmed decisions, derived index/ERD.Votes: 0GitHub stars: 3
- Start Workflow[Skill Management] Use when starting a detected workflow, initializing workflow state, or activating a workflow sequence.Votes: 0GitHub stars: 3
- Strategy Builder[Content] Use when a workflow step or the user asks for a marketing strategy: positioning, channels, messaging, campaigns, budget, KPIs.Votes: 0GitHub stars: 3
- Sync Codex[Codex] Use when running the full Codex mirror sync and verify pipeline, or when `.claude/**` edits leave `.agents/`, `.codex/` or `AGENTS.md` stale.Votes: 0GitHub stars: 3
- Sync Skills Shared Protocols[Skill Management] Use when shared protocol checklists change and need propagating across skills.Votes: 0GitHub stars: 3
- Tech Spec[Documentation] Use when generating the DERIVED technical spec view over code and tests, or reporting §8 TC drift. Generator only, never authors business content. generate|audit|sync.Votes: 0GitHub stars: 3
- Tech Stack Research[Architecture] Use when a workflow step or the user asks for tech stack options, researched and compared as a solution architect.Votes: 0GitHub stars: 3
- Test[Testing] Use when a workflow step or the user asks for a local test run: runs tests and analyzes the summary report.Votes: 0GitHub stars: 3
- Understand[Process] Use when a developer needs to understand and judge scoped work: a change set, subsystem, decision, plan or concept — flow, rationale, trade-offs, testing. Bugs: investigate --mode=debug; one feature''s code flow: investigate.Votes: 0GitHub stars: 3
- Watzup[Utilities] Use when a workflow step or the user asks for a session wrap-up: HTML report of what was done, changes, why; flags stale docs and lessons.Votes: 0GitHub stars: 3
- Web Design Guidelines[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance and UX best practices.Votes: 0GitHub stars: 3
- Web Research[Research] Use when a workflow step or the user asks for web research. Gathers and triages candidate sources; `--chain=deep-dive` also deep-dives them into an evidence base.Votes: 0GitHub stars: 3
- Why Review[Code Quality] Use when a workflow step or the user asks for rationale review: why needed/chosen, trade-offs, good idea or best practice. Only explicit rationale asks; not generic reviews or how-it-works. --fix-loop fixes/re-reviews.Votes: 0GitHub stars: 3
- Workflow Architecture Audit[Workflow] Use when auditing the whole project''s architecture or production readiness: read-only, one consolidated health report.Votes: 0GitHub stars: 3
- Workflow Big Feature[Workflow] Use when implementing a large, ambiguous, or research-driven feature.Votes: 0GitHub stars: 3
- Workflow Bugfix[Workflow] Use when fixing a bug, error, or crash — root-cause investigation, fix, verification.Votes: 0GitHub stars: 3
- Workflow Code To Spec[Workflow] Use when authoring or maintaining the canonical feature/spec artifact from existing code, keeping contract, implementation and tests in sync. Idea-to-spec: workflow-idea-to-spec.Votes: 0GitHub stars: 3
- Workflow E2e[Workflow] Use when writing, updating and verifying E2E tests through a bounded green fix/retest loop. --source={changes|recording|update-ui|prompt|context|whole}, --visual-review={true|false}.Votes: 0GitHub stars: 3
- Workflow End[Process] Use when ending the active workflow and clearing its state.Votes: 0GitHub stars: 3
- Workflow Feature Spec[Workflow] Use when creating or updating the configured canonical feature/spec artifact with its native paths, sections, identifiers and test-evidence carriers; portable 8-section/README/TC form only when no native profile applies.Votes: 0GitHub stars: 3