1328 hand-tested AI prompts across image, video, and music — each with full context, variables, and a sample output. Content is authored in Traditional Chinese; the UI here is English.
Installs a senior 'backend architect' subagent into Claude Code that uses contract-first design and domain-driven design to draw service boundaries, design REST/GraphQL/gRPC APIs, and build resilience and observability into the architecture from day one.
After Claude Code removed its built-in output style feature, this uses a SessionStart hook to automatically inject a custom response style (tone / format / rules) into every session, with a local marketplace for managing, activating, and applying multiple styles.
Brings obra/superpowers' "spec-first + true red-green TDD" development discipline into your agent: brainstorm to clarify requirements first, break the work into verifiable 2-5 minute tasks, then strictly follow RED-GREEN-REFACTOR, with a two-stage subagent review.
Rewrites awesome-cursorrules' FastAPI production architecture standard into an AGENTS.md/CLAUDE.md that enforces Router→Service→Repository layering, thin handlers, an anti-corruption layer, and idempotency — so AI automatically rejects anti-patterns when writing Python backends.
Anthropic's official mcp-builder: a four-phase workflow (research & planning → implementation → review & testing → writing evals) for wrapping your API or service into a high-quality MCP server. Covers both Python (FastMCP) and TypeScript (MCP SDK), with emphasis on tool naming, input/output schemas, error messages that point toward a fix, and evaluating with real-world tasks.
A curated, ready-to-use version of OneRedOak's design-review workflow: using Playwright MCP in a real browser environment, it automatically audits frontend changes across 7 stages (interaction, responsiveness, visuals, accessibility, robustness, code health) and reports findings graded Blocker/High/Medium/Nitpick.
Uses hooks in .claude/settings.json to automatically run formatting, linting, type-checking, or tests at specific Claude Code lifecycle events (PostToolUse after an edit, PreToolUse before running a command, Stop when wrapping up)—producing correct JSON config plus an executable hook script, with exit code 2 hard-blocking dangerous actions.
Has Claude Code break a large task into several independent, parallel subagents (each with its own context, restricted tools, and an assignable model), planning how to fan the work out, defining each subagent's responsibility boundaries and reporting format, and producing reusable .claude/agents subagent definition files when needed.
A large-refactor playbook for agents: first do a read-only survey of the 'blast radius' — which files, call sites, and tests are affected — then split the change into small batches, each preserving behavior, each run through its own tests, each its own atomic commit. Puts an end to 'change 40 files at once, then the build breaks and no one knows where to start fixing it.'