frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
tapestry
Unified content extraction and action planning. Use when user says "tapestry <URL>", "weave <URL>", "help me plan <URL>", "extract and plan <URL>", "make this actionable <URL>", or similar phrases indicating they want to extract content and create an action plan. Automatically detects content type (YouTube video, article, PDF) and processes accordingly.
archlinux-desktop-ops
仅用于 mainliufeng 的 Arch Linux / Hyprland 笔记本。用于管理 Hyprland workspace/window、蓝牙耳机连接与音频路由、触摸板异常恢复，以及调用 dotfiles 中已有桌面脚本；不要在 macOS 上使用。
computer-use-non-disruptive
Use before any Computer Use / @Computer / desktop app GUI operation, especially on macOS with Spaces/workspaces, multiple windows, background apps, or when the user asks not to be interrupted. Enforces non-disruptive Computer Use: do not switch workspace/window, do not activate apps, and prefer app accessibility-tree element operations.
draw-technical-diagrams
Turn technical explanations into precise, publication-ready architecture diagrams, flowcharts, sequence diagrams, hub-and-spoke maps, side-by-side comparisons, token/cache diagrams, and technical covers. Use when Codex must decide what diagram to draw, derive a diagram brief from domain knowledge, match the spatial layout of a reference image without copying its content or style, generate SVG/PNG assets, or fix broken arrows, crowded routing, text overflow, and mobile readability.
engineering-contract-guard
Lightweight contract preflight for software engineering changes. Use when modifying or designing APIs, DTOs, request/response schemas, OpenAPI/Swagger docs, gateway routes, SDK/client contracts, storage/query isolation fields, or cross-service interface boundaries. This skill checks compatibility and current facts before coding; it is not a full implementation workflow.
iteration-drift-guard
通用工程迭代防跑偏守卫。用于长期迭代、迁移/拆分、连续修同类 bug、prototype 转 production、本地联调补丁、AI 反复生成代码、架构边界变模糊，或用户提到“跑偏”“越改越乱”“codex一直在写”“连续修 bug”“迁移”“重构”“联调”“fix after fix”“migration”“refactor”“local integration”“gone off track”等场景。它要求实现前做一次简短的边界、不变量、正式入口、归属和测试闭环检查，避免补丁堆叠成架构漂移。单纯 API/DTO/schema/Swagger/gateway 兼容性检查优先使用 engineering-contract-guard。
notebooklm
通过 `notebooklm` CLI 直接访问 Google NotebookLM。支持 notebook/source/chat/artifact 全链路操作，包括报告、闪卡、脑图、数据表生成与导出，以及 source fulltext 提取。
spark
Use when the user invokes spark, asks to use the Spark model, wants a fast subagent, or wants quick low-risk side work such as code search, lightweight investigation, summarization, or fact-finding. This skill treats the invocation as an explicit request to spawn a GPT-5.3 Codex Spark subagent and summarize its findings.
vercel-design
Use Vercel-inspired DESIGN.md guidance as the preferred visual baseline for frontend UI design and implementation. Use when Codex is designing or building web app interfaces, SaaS/developer-tool dashboards, developer-platform landing pages, or when the user mentions Vercel style, getdesign.md, DESIGN.md, monochrome precision, Geist, or Vercel-like UI. Prefer this guidance over weak, generic, or inconsistent existing UI styling unless the project has a clearly stronger brand system or the user says otherwise.
agent-skill-manager
Install, update, audit, and compare skills across Codex, Hermes, and Pi using the local skill registry and fixed sync script.
devops-fullstack
DevOps for fullstack - Docker, CI/CD, deployment, monitoring
frontend-development
Frontend development - React, Vue, component architecture, state management
fullstack-basics
Full-stack development fundamentals - architecture, patterns, integration
backend-development
Backend development - APIs, authentication, business logic
database-integration
Database integration - schema design, queries, migrations, optimization
cc-explore
Research codebase and dependencies to support planning. Use when evidence is missing.
cc-plan
Create a concrete implementation plan with scope, risks, verification, and rollback. Use before any code changes.
cc-task
Implement based on an approved plan. Use after cc-plan is finalized.
humanizer
>
project-architect
>
to-issues
>
excalidraw-validated-diagram-generator
Generate validated Excalidraw diagrams and PNG exports from natural language descriptions. Use whenever the user asks to create, draw, visualize, diagram, make a flowchart, create an architecture diagram, generate an Excalidraw file, or export/validate a diagram as PNG. This skill combines generator-style Excalidraw JSON creation with a mandatory render-view-fix validation loop.
notion-formatter
>
open-knowledge-format
>
deep-research
Conduct systematic deep research on complex topics requiring multi-source analysis, synthesis, and actionable insights. Use when user needs thorough investigation beyond quick lookups.
git-commit
>
parallel-agents
>
pr-description
>
prompt-generator
>
code-reviewer
>
self-directed-exploration-guide
>
document-writer
>
design-patterns
>
agentic-backpressure
>
dependabot-review
>
shirushi
Document ID management for Git repositories. Validates, assigns, and tracks immutable doc_ids across Markdown/YAML files. Use when working with doc_id, document IDs, "@see docid" references, document integrity validation, or shirushi commands.
latex-writing
|
skill-management
IMPORTANT: Activate this skill BEFORE modifying any skill in ~/.claude/skills/. Guide for creating, updating, and maintaining Claude Code skills following best practices. Use proactively when: (1) creating a new skill, (2) modifying an existing skill in ~/.claude/skills/, (3) user requests to create, improve, update, review, or refactor a skill, (4) discussing skill quality or effectiveness. Always commit skill changes to the skills git repository after making modifications.
writing-crypto
|
try-first-tell-later
Structure educational content using try-first-tell-later pedagogy where students predict, attempt, or reflect before receiving explanations. Creates active learning through cognitive engagement and variation theory's contrast patterns. Use when writing educational materials, designing exercises, creating lecture notes, structuring tutorials, writing teaching examples with LaTeX/Beamer or Mentipy, developing problem sets, or when user mentions try-first, predict-first, productive failure, Socratic method, question-before-answer, exercise-driven learning, inquiry-based teaching, polls, or interactive slide questions.
update-project-docs
|
canvas-info
|
canvas-quiz
|
variation-theory
Apply variation theory of learning to structure content using contrast, generalization, and fusion patterns. Variation must target the critical aspects of the learning objective. Use proactively when (1) writing educational materials, explanations, tutorials, or lecture slides, (2) designing or reviewing examples in documentation, READMEs, or literate programs (.nw files), especially when multiple examples illustrate alternative approaches to the same task, (3) structuring code examples, CLI usage examples, or API examples where the reader should notice what differs between alternatives, (4) user mentions variation theory, learning theory, pedagogy, contrast, invariance, or critical aspects. Also activate when asked to elaborate, make concrete, or add examples to existing content. Works alongside literate-programming and didactic-notes skills; in educational LaTeX or .nw materials, keep variation-analysis labels in \ltnote{} rather than student-facing prose, unless the document itself is about that design.
literate-programming
CRITICAL: ALWAYS activate this skill BEFORE making ANY changes to .nw files. Use proactively when: (1) creating, editing, reviewing, or improving any .nw file, (2) planning to add/modify functionality in files with .nw extension, (3) user asks about literate quality, (4) user mentions noweb, literate programming, tangling, or weaving, (5) working in directories containing .nw files, (6) creating new modules/files that will be .nw format. Trigger phrases: 'create module', 'add feature', 'update', 'modify', 'fix' + any .nw file. Never edit .nw files directly without first activating this skill to ensure literate programming principles are applied. (project, gitignored)
didactic-notes
|
backing-claims
|
document-issues
IMPORTANT: load this skill the moment you notice an out-of-scope follow-up while working, and BEFORE filing any GitHub issue or importing to nytid todo. Captures unrelated follow-up issues discovered during repository work and records them for later. Use proactively when: (1) working inside a git repository and you spot a bug, cleanup, missing test/doc, or tech-debt item that is NOT part of the current task (even one you only mention in a comment, memory, or summary — capture it here instead); (2) the user mentions filing an issue, follow-up, backlog item, or nytid import. Prefer gh issue; ask before creating anything unless autonomous issue capture is enabled; optionally import created GitHub issues into nytid todo.
Page 1416 of 1711 · 85546 results
