DietrichGebert/ponytailPlugins
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
138k
1 add
Claude Code plugin for agents, skills, and hooks
WIGTN Plugins is a Claude Code plugin bundle that adds a structured workflow from idea to verified commit. It includes commands for PRDs, screen specs, implementation, review, and auto-commit, plus specialized agents, shared memory, skills, and hooks.
45 stars•2 forks•Python•Updated 9d ago
Who it's for
Builders who use Claude Code and want a repeatable path from feature idea to checked-in code.
What it delivers
You can turn a vague feature idea into a planned build, reviewed changes, and a commit with checks passed.
What it does
PRD and task planning
`/prd` turns a feature idea into a contract-based PRD and phased task plan, including UI sections when needed.
Screen spec workflow
`/screen-spec` produces IA, user flow, screen spec, clickable wireframe HTML, and dev handoff for UI work.
Parallel implementation teams
`/implement` dispatches backend, frontend, AI, and ops work in parallel when tasks are independent.
Evidence-based review
`/auto-commit` runs code review findings through PASS/WARN/FAIL gating before commit and push.
Claude Code hooks
Pre-tool and post-tool hooks block dangerous commands and remind you about pipeline completion and formatting.
Packaged agents and skills
The plugin ships 11 agents for coordination, development, review, and design discovery, plus 6 reusable skills.
How to get it
- 1Run
# Install /plugin marketplace add wigtn/wigtn-plugins /install wigtn-plugins # Try it — this is the full workflow /prd landing page for an AI startup with modern design /implement ai-landing /auto-commit
README
Why WIGTN-Coding?
Without this plugin: You open Claude Code → write a vague prompt → get generic code → spend 30 min fixing → repeat.
With WIGTN-Coding:
You run /prd → get a structured contract → generate screen specifications when needed → implement → commit only after the configured checks pass.
What it does
WIGTN Plugins is a Claude Code plugin with 11 specialized agents for requirements, architecture, implementation, and review. It uses parallel work only where tasks are independent, and carries one contract from PRD through commit.
/prd "SaaS dashboard with OAuth" → Contract-based PRD + task plan
/screen-spec dashboard → (if UI) IA + flow + screen spec + clickable wireframe HTML
/implement --parallel → Backend + Frontend + AI + Ops teams build simultaneously
/auto-commit → Findings rollup + objective checks + commit
Quick Start
# Install
/plugin marketplace add wigtn/wigtn-plugins
/install wigtn-plugins
# Try it — this is the full workflow
/prd landing page for an AI startup with modern design
/implement ai-landing
/auto-commit
That's it. The plugin handles PRD generation, 4-category quality analysis, architecture decisions, design style selection, parallel build, code review, and commit.
The Pipeline
┌─────────────────────────────────────────────────────────────────────────────┐
│ /prd "SaaS dashboard with OAuth" │
│ │
│ 1. Context Gathering ─── scan project structure, tech stack, package.json │
│ 2. AskUserQuestion ───── Scale Grade? (Hobby / Startup / Growth / Enterprise) │
│ 3. PRD Generation ────── PRD_{feature}.md (7 sections, Gherkin stories) │
│ 4. Task Planning ─────── PLAN_{feature}.md (phases + tasks) │
│ │
│ ┌─── prd-reviewer — 4 adversarial lenses ────────────────────────────┐ │
│ │ Phase 0: Context Harvest (CLAUDE.md, code patterns, deps) │ │
│ │ Phase 1: PRD Structure Parsing │ │
│ │ Phase 2: ═════════════ 4 ADVERSARIAL LENSES ══════════ │ │
│ │ │ Completeness │ Feasibility │ Security │ Consistency │ │ │
│ │ │ FR/NFR/edge │ stack fit │ OWASP │ naming/arch │ │ │
│ │ │ cases, dups │ blast radius│ auth/z │ PRD↔code │ │ │
│ │ Phase 3: Cross-Category Synthesis (compound risks) │ │
│ │ Phase 4: Quality Gate ─── PASS / WARN / BLOCKED │ │
│ └────────────────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────────────────┘
│
BLOCKED → stop
│ PASS / WARN
▼
┌─────────────────────────────────────────────────────────────────────────────┐
│ /implement ai-landing │
│ │
│ ┌─── DESIGN PHASE ──────────────────────────────────────────────────┐ │
│ │ ═══════════════ 3 AGENTS IN PARALLEL ═══════════════ │ │
│ │ │ Agent A │ Agent B │ Agent C │ │ │
│ │ │ PRD load + │ architecture-decision│ Project scan + │ │ │
│ │ │ quality gate │ Mono/Modular/MSA │ gap analysis │ │ │
│ │ ══════════════════════════════════════════════════════════════ │ │
│ │ │ │ │
│ │ Team Allocation ─────── pattern match files → teams │ │
│ │ api/, services/ → Backend │ │
│ │ components/, app/ → Frontend │ │
│ │ ai/, llm/ → AI Server │ │
│ │ Dockerfile, CI/ → Ops │ │
│ │ │ │
│ │ Design Discovery (Frontend only, if no existing style) ──────── │ │
│ │ VS technique: 4 questions → suitability % per style → select │ │
│ │ │ │
│ │ ✋ CHECKPOINT: AskUserQuestion ── proceed / review / cancel │ │
│ └───────────────────────────────────────────────────────────────────┘ │
│ │
│ ┌─── BUILD PHASE ─── team-build-coordinator ────────────────────────┐ │
│ │ │ │
│ │ Phase 0: Setup ─── SHARED_CONTEXT_{feature}.md + PLAN ledger │ │
│ │ Context Harvest: sample existing code → learn patterns │ │
│ │ │ │
│ │ Phase 1: Foundation (if Backend + dependents exist) │ │
│ │ Backend writes: DB schema, shared types, API contracts │ │
│ │ ↓ unblocks other teams │ │
│ │ │ │
│ │ Phase 2: ════════════ UP TO 4 TEAMS IN PARALLEL ════════════ │ │
│ │ │ BACKEND │ FRONTEND │ AI SERVER │ OPS │ │
│ │ │ backend- │ frontend- │ ai-agent │ gen │ │
│ │ │ architect │ developer │ │ pur │ │
│ │ │ │ + style guide │ │ │ │
│ │ │ API, services │ pages, comps │ LLM, STT │ CI │ │
│ │ │ DB, middleware │ state, styling │ prompts │ CD │ │
│ │ ════════════════════════════════════════════════════ │ │
│ │ ▲ reads │ writes │ │
│ │ └──── SHARED_CONTEXT ────┘ │ │
│ │ │ │
│ │ Phase 3: Integration ─── API contract match, type consistency, │ │
│ │ pattern verification vs Phase 0 learned patterns │ │
│ │ │ │
│ │ Phase 4: Build & Test ─── typecheck + test + build │ │
│ └───────────────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────────────────┐
│ /auto-commit │
│ │
│ Step 1: Branch Strategy │
│ on feature branch → reuse │ on main + PLAN → feat/<name> │
│ │
│ Step 2: Quality Gate │
│ ┌─── code-reviewer — evidence-backed findings ───────────────────┐ │
│ │ Each finding: file + line + severity + confidence + evidence │ │
│ │ │ │
│ │ FAIL ← critical ≥1 │ │
│ │ WARN ← critical 0 AND (major ≥1 OR minor ≥5) │ │
│ │ PASS ← critical 0 AND major 0 AND minor <5 │ │
│ └─────────────────────────────────────────────────────────────────┘ │
│ │
│ Step 3: Objective Checks ─── typecheck / lint / configured checks │
│ non-zero exit → blocked │
│ Step 4: Commit Message ─── <type>(<scope>): <subject> + gate result │
│ ✋ CHECKPOINT: AskUserQuestion ── PR / Draft PR / Commit only / Cancel │
│ Step 5: git commit → git push -u → gh pr create │
└─────────────────────────────────────────────────────────────────────────────┘
Shared Memory (3 layers):
Layer 1 — MEMORY.md ─────────── persistent cross-session conventions
Layer 2 — SHARED_CONTEXT ────── session-scoped API contracts, types, patterns
Layer 3 — PLAN ledger ───────── task checkboxes + execution log
Independent steps can run in parallel; dependent steps remain ordered. Runtime varies with the task, model, and configured checks.
Commands
| Command | What it does |
|---|---|
/prd <feature> | Generate PRD + phased task plan from a feature idea (now includes User Roles, Page State Matrix, User Flow sections for UI features) |
/screen-spec <feature> | Optional UI gate: IA + User Flow + Screen Spec + clickable HTML wireframe + Dev Handoff. Lo-fi wireframe (grayscale + semantic colors); style is decided later at /implement |
/implement <feature> | Design + build with automatic parallel team dispatch (consumes screen-spec output if present) |
/auto-commit | Evidence-backed findings → deterministic rollup → objective checks → commit + PR |
/review-pr <PR> | Review a GitHub PR from terminal: diff analysis, severity findings, inline comments |
Agents (11) — click to expand
Coordinators
| Agent | Role |
|---|---|
team-build-coordinator | Dispatches Backend, Frontend, AI, Ops teams in parallel |
architecture-decision | MSA vs Monolithic vs Modular Monolith |
Developers
| Agent | Role |
|---|---|
frontend-developer | React 19, Next.js 16+, 20 design styles |
backend-architect | API design, database schema, backend patterns |
mobile-developer | React Native / Expo, native modules |
ai-agent | WhisperX STT, OpenAI/Anthropic integration |
Quality
| Agent | Role |
|---|---|
code-reviewer | Evidence-backed findings with deterministic PASS/WARN/FAIL rollup |
pr-reviewer | GitHub PR diff review, severity findings, inline review comments (used by /review-pr) |
prd-reviewer | Finds gaps across completeness, feasibility, security, consistency |
code-formatter | Multi-language auto-formatting and lint fixes |
design-discovery | VS-based style recommendation for Web and Mobile |
Skills (6) — click to expand
| Skill | What it provides |
|---|---|
code-review-levels | Deep review (Level 3: call chains, edge cases, concurrency) and architecture review (Level 4: SOLID, layer violations, scalability) |
design-system-reference | 20 style guides with typography, color, components, motion, and anti-patterns. Works with design-discovery for context-aware recommendations |
handdrawn-diagram | Generates a hand-drawn (sketch-style) architecture or flow diagram as committable SVG + PNG via Mermaid look:handDrawn. Renders identically on README, GitHub, Devpost, and slides |
screen-spec | Generates 5 UI artifacts from PRD — IA, User Flow, Screen Spec, clickable Wireframe HTML, Dev Handoff. Lo-fi wireframe (grayscale + semantic colors); style decisions deferred to /implement. Invoked by /screen-spec |
team-memory-protocol | SHARED_CONTEXT management for cross-agent coordination during parallel builds |
wigtn-ppt | Generates a WIGTN-brand HTML presentation (Light/Dark themes) from brand tokens — no template needed. Signature purple dot on every slide, with a CSS/SVG wordmark fallback when logo assets are absent |
Design Styles (20) — click to expand
Each style guide covers philosophy, typography, layout, color, components, motion, and an anti-pattern checklist.
| Style | Vibe |
|---|---|
| Editorial | Magazine layouts, strong serif typography |
| Brutalist | Raw, bold, unconventional |
| Glassmorphism | Frosted glass, blur, transparency |
| Swiss Minimal | Grid-based, typography-focused |
| Neomorphism | Soft UI, inset/outset shadows |
| Bento Grid | Card-based grid (Apple-inspired) |
| Dark Mode First | Dark interfaces from the ground up |
| Minimal Corporate | Clean professional aesthetic |
| Retro Pixel | CRT effects, monospace, terminal nostalgia |
| Organic Shapes | Blobs, natural curves, earthy tones |
| Maximalist | Bold type, intense colors, layered |
| 3D Immersive | CSS 3D transforms, parallax, depth |
| Liquid Glass | Fluid translucent glass, dynamic reflections |
| Claymorphism | Soft 3D clay elements, pastel tones |
| Minimalism | Extreme simplicity, whitespace-driven |
| Neobrutalism | Colorful accents, bold borders |
| Skeuomorphism | Realistic textures, physical metaphors |
| Aurora / Gradient Mesh | Mesh gradients, ambient glow, ethereal |
| Terminal / Hacker | Monospace-driven, information-dense, semantic color |
| Kinetic Typography | Scroll-driven text animation, split reveals |
The design-discovery agent recommends the best style for your project context using VS (Verbalized Sampling).
Hooks (4) — click to expand
| Hook | Trigger | What it does |
|---|---|---|
| Dangerous Command Blocker | Bash PreToolUse | Blocks rm -rf /, git push --force, DROP TABLE |
| Pipeline Completion | Stop | Reminds to review before pushing |
| Frontend Formatting | Write|Edit PostToolUse | Reminds prettier/eslint for .tsx, .jsx, .css |
| Backend Pattern Compliance | Write|Edit PostToolUse | Checks error handling, validation, logging for .ts, .py, .go |
Scenarios
Full-Stack SaaS from scratch
/prd project management tool with kanban boards and team collaboration
# → 4-lens analysis catches: "Missing: real-time sync, role permissions"
/implement --parallel project-management
# Backend: API endpoints, Prisma schema, auth middleware
# Frontend: Kanban board, team views, dashboard
# Ops: Dockerfile, GitHub Actions CI/CD
/auto-commit
# findings rollup PASS + objective checks pass → auto-commit
Mobile app with React Native
/prd fitness tracker with workout logging, progress charts, Apple Health sync
/implement fitness-tracker
# Expo Router + Zustand + MMKV + React Query
# Biometric auth, haptic feedback, offline sync
Design-driven landing page
/prd AI startup landing page with modern design
/implement ai-landing
# design-discovery activates → recommends Glassmorphism or Liquid Glass
# Frontend team builds Hero, Features, Pricing, CTA with chosen style
Backend API + AI features
/prd transcription service with WhisperX STT and LLM summarization
/implement --parallel transcription-service
# Backend → API + DB + auth
# AI → WhisperX + OpenAI/Anthropic patterns
# Frontend → Upload UI + transcription viewer
Tech Stack
| Domain | Technologies |
|---|---|
| Frontend | React 19, Next.js 16+, Tailwind CSS, Radix UI |
| Backend | NestJS, Express, FastAPI, Prisma, Drizzle |
| Mobile | React Native 0.73+, Expo SDK 52+ |
| AI | WhisperX, OpenAI GPT, Anthropic Claude |
| DevOps | Docker, Kubernetes, GitHub Actions |
| Design | 20 style systems, VS-based discovery, HIG, MD3 |
Contributing
git checkout -b feature/amazing-skill
# make changes
git commit -m 'feat: Add amazing skill'
git push origin feature/amazing-skill
# open PR
License
Apache License 2.0 — see LICENSE.
Built by WIGTN Crew
5 AI engineers. We don't study AI — we ship it.
Files in the repo
Repository payload•12 top-level entries
- .claude-plugin
- .github
- plugins
- .gitattributes
- .gitignore
- CITATION.cff
- CLAUDE.md
- CONTRIBUTING.md
- LICENSE
- README.cn.md
- README.ko.md
- README.md
Discussion (0)
Ask about usage, or say what you built with itSign in to join the discussion.
No comments yet. Be the first to say what this is good for.
More plugins
Graphs that teach > graphs that impress. Turn any code into an interactive knowledge graph you can explore, search, and ask questions about. Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more.
82k
code-yeongyu/
oh-my-openagent
code-yeongyu/oh-my-openagentPlugins
OmO: Just type "mass ulw" keyword with your prompt. Now you are the master of graph engineering.
69k
thedotmack/claude-memPlugins
Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
94k
dmmulroy/anti-slopPlugins
Opinionated Oxlint rules for rejecting low-evidence TypeScript and JavaScript patterns
4.3k
Yeachan-Heo/oh-my-claudecodePlugins
Teams-first Multi-agent orchestration for Claude Code
39k