REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
★ Stars are for the whole repo, not each skill
This repo is a collection of 31 skills
Development workflows for Claude Code that keep broad exploration focused on the outcome you approved.Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.
[](https://mcp.popnx.com/en/skills/shinpr-claude-code-workflows)MCP-Server, die die KI für dieselbe Arbeit mit Diensten verbinden
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
Gleiche Art Arbeit, sortiert wie die Skill-Liste
| Dieser claude-code-workflows | rea | graphify | archify | security-audit-skill | |
|---|---|---|---|---|---|
| Anbieter | shinpr | morluto | Graphify-Labs | tt-a1i | cloudflare |
| Skills | 31 | 1 | 1 | 1 | 1 |
| GitHub-Sterne | 717 | 461.751 | 148.352 | 96.757 | 73.156 |
| Letzte Codeänderung | 11. Nov. 2026 | 16. Nov. 2026 | 16. Nov. 2026 | 15. Nov. 2026 | 15. Sept. 2026 |
| Lizenz | MIT | MIT | Apache-2.0 | Apache-2.0 | MIT |
31 Skills (Anweisungssammlungen) von shinpr, die eine KI liest und befolgt · kein MCP-Server
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
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.
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
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.
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…
No description from the maker
Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.
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.
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.
Add integration/E2E tests to existing codebase using Design Docs
Execute materialized task files in autonomous execution mode
Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval
Investigate problem, verify findings, and derive solutions
Orchestrate the complete implementation lifecycle from requirements to deployment
Create work plan from design document and obtain plan approval
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow
Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved corrections.
No description from the maker
Update existing design documents (Design Doc / PRD / ADR) with review
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.
No description from the maker
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.
No description from the maker
MCP = die Hände
Verbindet die KI mit einem externen Dienst oder Daten, etwa Notion lesen oder eine Rechnung erstellen. Ein Programm oder Server muss laufen.
Skill = das Handbuch
Eine Textdatei, die der KI zeigt, wie eine Aufgabe geht. Sie verbindet sich mit nichts.
Manches überschneidet sich: Einige Skills starten Skripte mit Werkzeugen, einige MCP-Server liefern nur Wissen. Geh von der Aufgabe aus.
Claude CodeClaude (เว็บ/แอป)Codex
Laut README des Anbieters und den Ordnern im Repo
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
Befehle werden geprüft · Kopier-Buttons erscheinen, sobald sie bestanden sind
Aus dem README des Anbieters; lädt den Code des Anbieters herunter und führt ihn aus
Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.