claude-code-workflows Skill
★ Stars are for the whole repo, not each skill
What it does
This repo is a collection of 31 skills
- Connects Instruction files the AI reads; connects to nothing
- Account or key No key needed
- Category Coding
Maker’s original description
Development workflows for Claude Code that keep broad exploration focused on the outcome you approved.For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/shinpr-claude-code-workflows)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one claude-code-workflows | rea | graphify | archify | security-audit-skill | |
|---|---|---|---|---|---|
| Maker | shinpr | morluto | Graphify-Labs | tt-a1i | cloudflare |
| Skills | 31 | 1 | 1 | 1 | 1 |
| GitHub stars | 717 | 461,751 | 148,352 | 96,757 | 73,156 |
| Last code change | Nov 11, 2026 | Nov 16, 2026 | Nov 16, 2026 | Nov 15, 2026 | Sep 15, 2026 |
| License | MIT | MIT | Apache-2.0 | Apache-2.0 | MIT |
31 skills (instruction sets) by shinpr that an AI reads and follows · not an MCP server
Pick the skill to install
Install only the ones you use. Open a skill to see how to install it
This set has 31 skills, too many to install at once: every installed skill’s description loads into every chat, so the AI picks the wrong one more easily. Pick only the ones you use from the list below
Showing 22 of 31 See all on GitHub
- ai-development-guide
Applies technical decision criteria, anti-pattern detection, debugging, and quality gates for backend and frontend code. Use when implementing, reviewing, or diagnosing code, code smells, failures, or implementation completeness.
- coding-principles
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
- documentation-criteria
Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.
- external-resource-context
Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the user mentions design source, design system, API schema, Ia…
- frontend-ai-guide
No description from the maker
- implementation-approach
Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.
- integration-e2e-testing
Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when generating or consuming test skeletons or reviewing shared mutation routes.
- llm-friendly-context
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
- recipe-add-integration-tests
Add integration/E2E tests to existing codebase using Design Docs
- recipe-build
Execute materialized task files in autonomous execution mode
- recipe-design
Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval
- recipe-diagnose
Investigate problem, verify findings, and derive solutions
- recipe-implement
Orchestrate the complete implementation lifecycle from requirements to deployment
- recipe-plan
Create work plan from design document and obtain plan approval
- recipe-reverse-engineer
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow
- recipe-review
Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved corrections.
- recipe-task
No description from the maker
- recipe-update-doc
Update existing design documents (Design Doc / PRD / ADR) with review
- requirement-convergence
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from decision-relevant repository evidence. Use when a requirement enters a workflow, before design begins.
- test-implement
No description from the maker
- testing-principles
Language-agnostic testing principles for choosing which tests a change needs, test quality, and proof ownership, including frontend and browser E2E tests. Use when writing tests, deciding test scope, or reviewing test quality.
- typescript-rules
No description from the maker
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeClaude (เว็บ/แอป)Codex
From the maker’s README and the folders in the repo
Install
Pick a skill first
This repo has 31 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP
The maker’s command installs the whole set of 31
Checking the commands · copy buttons appear once they pass
Copied from the maker’s README; it downloads and runs the maker’s code
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 717
Stars are for the whole repo, not each skill - Maker
- shinpr
- License
- MIT
- Last code change
- Nov 11, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 30
- Topics
- agent-skills, agentic-ai, agentic-coding, ai-agents, anthropic, claude-code, claude-code-plugin, claude-code-skill, code-quality, code-review, developer-tools, development-workflow