Loading...
Loading...
Found 54 Skills
Xử lý khi Data Model trong delta spec của OpenSpec (openspec/changes/<change-name>/specs/) thay đổi so với spec đã archive (openspec/specs/) - thêm/xóa/sửa field, đổi kiểu dữ liệu - để tránh crash do local database (Hive/SQFLite/Drift) hoặc parse JSON API bị lệch schema cũ. LUÔN dùng skill này TRƯỚC KHI sinh code, ngay khi phát hiện Data Model mới khác với model hiện có trong code.
Fact-checks OpenSpec user documentation with a fresh-context subagent that re-runs commands and checks claims against source. Manually triggered; not part of the drafting loop. Use when the user asks to verify, fact-check, or accuracy-check a docs page, section, or set of changed claims.
Collaborative page-drafting mode for the OpenSpec docs. Builds a scratch plan inside the target page (purpose, structure, numbered draft steps), iterates on it with the user, then drafts one section per approved step and cleans up after itself. Use when a page needs a from-scratch rewrite or a new page is being shaped with the user in the loop.
Complete Java Spring Boot skill set for building enterprise applications. Includes modular architecture with optional components: - PostgreSQL database with JPA/Hibernate + Flyway migration - Redis caching (optional) - Kafka/RabbitMQ messaging (optional, choose one) - JWT + OAuth2 authentication (optional OAuth2) - RBAC authorization (optional) - TDD with Mockito - Spec-First Development with OpenSpec
Use when you need to ship a single PR-sized feature end-to-end (plan -> implement -> verify) with artifacts. Ship core product features quickly in a Next.js codebase: turn a feature idea into an executable plan, implement in PR-sized slices, and keep artifacts under runs/ (or OpenSpec changes/ when available). Supports plan-only mode for early scoping. For prototype UI work, include a demo-ready wow moment (animation/micro-interaction) by default unless user opts out.
Use this skill for project schedule management — tracking modules, milestones, and delivery phases stored in YAML. Invoke whenever the user asks about: project progress or delivery status, module status (planned/in_progress/done/deferred), weekly task breakdown, milestone countdowns, risk analysis, linking OpenSpec changes to modules, or syncing schedule data to Yunxiao. Triggers on: "planning", "schedule", "progress", "milestone", "what's this week", "what's left", "mark as done", "排期", "进度", "本周任务", "里程碑", "模块状态", "还剩多少". Do NOT trigger for: calendar reminders, weekly work reports, or Yunxiao tasks without schedule context.
Improve skills and workflows by analyzing run artifacts and execution logs (events.jsonl/state.json) under runs/ (or OpenSpec changes/). Use when you want to iterate on skills based on real runs: find failure modes, bottlenecks, unclear prompts, missing I/O contracts, and propose concrete edits.
Ship Faster end-to-end workflow for small web apps (default: Next.js 16.1.1): idea/prototype → foundation gate → design-system.md → lightweight guardrails + docs → feature iteration → optional Supabase + Stripe → optional GitHub + Vercel deploy → optional AI-era SEO (sitemap/robots/llms.txt). Resumable, artifact-first under runs/ship-faster/ (or OpenSpec changes/). Trigger: ship/launch/deploy/production-ready MVP.
Enforces spec-before-code workflow for AI-driven development. Automatically selects Spec-Kit or OpenSpec mode, triages complexity (quick/standard/thorough), recovers session context, and applies quality gates (G0-G4) with automated review loops at every stage. Use this skill whenever the user says "/super-spec", "spec first", "规范先行", or starts any feature, bugfix, or refactor — especially in projects with .spec-mode, .specify/, or openspec/ directories. Even if the user doesn't explicitly ask for spec-driven workflow, activate this skill for any non-trivial code change to prevent skipping the design phase. Orchestrates: Spec-Kit/OpenSpec (OPSX) + planning-with-files + ui-ux-pro-max (v2.0, 67 styles, 161 palettes, 13 stacks) + Superpowers (TDD, code review, verification, debugging, spec/plan review loops, subagent model selection).
Use when creating or iterating on a detailed per-subsystem technical design specification from a system spec, before starting OpenSpec workflow. Triggers: "design spec", "subsystem spec", "write the spec for S1", "phase breakdown", "implementation phases", "mid-level spec", "technical design". Encodes opinionated progressive phase discipline with FP progression and contract boundaries. Do NOT use for high-level system specs (use brainstorming) or for OpenSpec artifacts (use openspec directly).
Initialize Spec-Driven Development context in any project. Detects stack, conventions, and bootstraps the active persistence backend. Trigger: When user wants to initialize SDD in a project, or says "sdd init", "iniciar sdd", "openspec init".
Break down a change into an implementation task checklist. Trigger: When the orchestrator launches you to create or update the task breakdown for a change.