web-dev-skills

Run a single demo E2E test file, diagnose failures, dispatch fixes to agents, and re-run until pass.

Execute phased task plans by dispatching work to specialized sub-agents for backend, frontend, miniapp, Flutter, or demo phases.

Validate task plan executability and consistency with a 100-point score and P0/P1/P2 fix list.

Convert technical design documents into executable phased task plans with ordered work breakdown.

Evaluate technical design documents for implementability, completeness, and consistency with a quantitative 100-point score.

Initialize a full-stack project skeleton with Rust backend (Axum + SeaORM + Redis) and React frontend (TypeScript + TanStack + Tailwind).

Generate technical design documents including API design, database schema, and implementation details for a feature.

Generate project tutorial documentation that reads like a human wrote it, not like AI output. Scans the codebase, extracts architecture/APIs/config/deployment details, and writes structured tutorial docs in the project's documentation target, preferring an existing docs-web site over docs/tutorials/. Use this skill whenever the user asks to write project docs, tutorials, getting-started guides, API references, deployment guides, onboarding docs, or any kind of project walkthrough. Also trigger when they say "write documentation", "generate docs", "create a tutorial", "onboarding guide", "write a guide", or want help producing readable documentation for a project or module — even if they don't explicitly say "tutorial."

由 AI 基于 git diff 总结提交内容，使用脚本运行受影响区域 CI，通过后 git commit && git push。

After implementation and acceptance, summarize the draft PRD against delivered facts, then revise the existing formal PRD.

Organize and realign PRDs, user stories, design/task docs, implementation facts, and project structure so the target project keeps a clean current context instead of accumulating stale or misleading information. Use when asked to audit documentation drift, structure drift, traceability gaps, whether PRD/code/test/demo directory organization and module boundaries are reasonable, or to merge/prune/rewrite PRDs into concise current authority sources.

Decide whether a feature should enter the t-tools workflow before tech research or PRD.

Generate HTML Preview for any Markdown document, helping humans quickly understand content.

Validate draft PRD, published PRD baseline, and user stories for quality and consistency.

Create or update draft PRD and user stories for a feature.

Assess technical feasibility for a feature. Scans codebase, checks dependencies, researches libraries, and writes a structured report under .ai/tech-research/.

Validate demo tests cover user stories, compile and pass, and output structured acceptance reports.

Discover and run all demo E2E tests sequentially with auto-fix support and summary report generation.

Bump project version, create git tag, and push release commit to remote.