Loading...
Loading...
Found 12,395 Skills
Interview the user in depth about what they actually want to build, then scaffold a working full-stack web app around it. Use when the user wants to start a new app, website, prototype, or SaaS; when they don't know what tech stack to pick; or when they want a solid working starting point fast. Covers requirements discovery, project setup, database (SQLite or Postgres in Docker), sign-in, transactional email, file uploads, payments, AI features, background jobs, optional agent access over MCP so tools like Claude can use the app, a real landing page and dashboard, optional public help documentation, a design system agreed with the user and written to DESIGN.md so every page matches, an account settings area with system logs and debugging built in, the legal pages and cookie consent an app of that kind actually owes its users, whether search engines and AI crawlers should find it at all, and a closing pass that proves the result actually builds, serves and does what was agreed rather than taking the builder's word for it.
Review Kanban handoffs and route verified outcomes.
This skill is to be used when users explicitly request to 'verify/optimize in-text citations in the review `{topic}_review.tex`', 'run research-citation-check', or request to use the old name check-review-alignment skill. It uses the host AI's semantic understanding to verify each citation against the corresponding literature content one by one. Only when a fatal citation error is detected will the 'sentence containing the citation' be minimally rewritten. It prioritizes reusing the rendering script of `research-literature-review` to output PDF/Word, and allows fallback to the old name systematic-literature-review during the transition period. Core principle: Do not make changes for the sake of changing; when it is impossible to determine whether it is a fatal error, keep the original content and issue a warning in the report. ⚠️ Not applicable: When users only want to generate the main body of a systematic review (should use research-literature-review); when users only want to add/verify BibTeX entries (should use the dedicated bib management process).
Weekly Report Generation. Collect this week's git commits and work items supplemented by users, organize them into a structured Chinese weekly report with sections 'Completed/In Progress/Risks/Next Steps'. Facts are based on commits, no fabrication. Use to generate a weekly report from git history and work items.
Builds a project and Ship it to the target environment
Use when recording a narrated screencast or video tutorial that shows how to set up or configure a Drupal module, capturing a ddev site in the browser at 1920x1080 with a visible mouse cursor, typed form input, ElevenLabs voice-over, and a caption bar, then muxing and concatenating the scenes into one MP4.
Create, audit, shorten, or scope AGENTS.md and CLAUDE.md instructions. Use writing-skills for on-demand skills; excludes human-facing documentation and READMEs.
Use when reviewing metered usage invoices against usage exports, pricing rules, minimum commitments, credits, customer entitlements, and billing exceptions.
Break a PRD into independently-workable issues and write each as a local markdown file in issues/. Use when the user wants to turn a PRD into a list of concrete tasks.
Turn a game idea into a focused design problem, risk-first prototype plan, and iteration loop. Use when starting a game, choosing what to build first, scoping an MVP, defining design questions, planning prototypes, or deciding whether an idea is ready for production.
Research link-building opportunities by mapping assets to opportunity types, building query libraries, analyzing competitor backlinks, finding scrapeable lists, and expanding prospecting seeds. Use when finding link prospects, creating link prospecting queries, mapping guest post/resource/directory opportunities, or producing a prospect research map before qualification or outreach.
Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug reports, and user follow-up. Use when setting up docs feedback channels, triaging docs issues, responding to frustrated users, prioritizing doc fixes, or converting feedback into actionable documentation work.