Topic: codex
8,457 skills in this topic.
-
community-marketing
coreyhaines31/marketingskills 18,393
-
aso-audit
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.
coreyhaines31/marketingskills 18,393
-
ctx-purge
Purge the context-mode knowledge base. Permanently deletes all indexed content
and resets session stats. This is destructive and cannot be undone.
Trigger: /context-mode:ctx-purge
mksglu/context-mode 7,081
-
context-mode-ops
Manage context-mode GitHub issues, PRs, releases, and marketing with parallel subagent army. Orchestrates 10-20 dynamic agents per task. Use when triaging issues, reviewing PRs, releasing versions, writing LinkedIn posts, announcing releases, fixing bugs, merging contributions, validating ENV vars, testing adapters, or syncing branches.
mksglu/context-mode 7,081
-
ctx-upgrade
Update context-mode from GitHub and fix hooks/settings.
Pulls latest, builds, installs, updates npm global, configures hooks.
Trigger: /context-mode:ctx-upgrade
mksglu/context-mode 7,081
-
ctx-stats
Show how much context window context-mode saved this session.
Displays token consumption, context savings ratio, and per-tool breakdown.
Read-only — shows stats only, no reset capability.
To wipe the knowledge base entirely, use ctx_purge instead.
Trigger: /context-mode:ctx-stats
mksglu/context-mode 7,081
-
context-mode
Use context-mode tools (ctx_execute, ctx_execute_file) instead of Bash/cat when processing
large outputs. Triggers: "analyze logs", "summarize output", "process data",
"parse JSON", "filter results", "extract errors", "check build output",
"analyze dependencies", "process API response", "large file analysis",
"page snapshot", "browser snapshot", "DOM structure", "inspect page",
"accessibility tree", "Playwright snapshot",
"run tests", "test output", "coverage report", "git log", "recent commits",
"diff between branches", "list containers", "pod status", "disk usage",
"fetch docs", "API reference", "index documentation",
"call API", "check response", "query results",
"find TODOs", "count lines", "codebase statistics", "security audit",
"outdated packages", "dependency tree", "cloud resources", "CI/CD output".
Also triggers on ANY MCP tool output that may exceed 20 lines.
Subagent routing is handled automatically via PreToolUse hook.
mksglu/context-mode 7,081
-
ctx-doctor
Run context-mode diagnostics. Checks runtimes, hooks, FTS5,
plugin registration, npm and marketplace versions.
Trigger: /context-mode:ctx-doctor
mksglu/context-mode 7,081
-
finish-work
Pre-commit quality checklist covering lint, typecheck, tests, code-spec sync, API changes, database migrations, cross-layer verification, and manual testing. Blocks commit if infra or cross-layer specs lack executable depth. Use when code is written and tested but not yet committed, before submitting changes, or as a final review before git commit.
mindfold-ai/Trellis 5,124
-
break-loop
Deep post-fix bug analysis across five dimensions: root cause categorization, fix failure analysis, prevention mechanisms, systematic expansion, and knowledge capture. Updates .trellis/spec/ guides with lessons learned to prevent recurring bugs. Use when a debugging session completes, after fixing a tricky bug, when the same class of bug keeps recurring, or when you want to capture debugging insights into project documentation.
mindfold-ai/Trellis 5,124
-
trellis-bootstrap
Initialize Trellis AI workflow system in a project. Use when user mentions "Trellis", "初始化 Trellis", "setup Trellis", "install Trellis", or wants to add AI-assisted development workflow to their project. This is a one-time setup skill.
mindfold-ai/Trellis 5,124
-
check
Validates recently written code against project-specific development guidelines from .trellis/spec/. Identifies changed files via git diff, discovers applicable spec modules, runs lint and typecheck, and reports guideline violations. Use when code is written and needs quality verification, to catch context drift during long sessions, or before committing changes.
mindfold-ai/Trellis 5,124
-
create-command
Scaffolds a new skill file with proper naming conventions and structure. Analyzes requirements to determine skill type and generates appropriate content. Use when adding a new developer workflow skill, creating a custom skill, or extending the Trellis skill set.
mindfold-ai/Trellis 5,124
-
record-session
Records completed work progress to .trellis/workspace/ journal files after human testing and commit. Captures session summaries, commit hashes, and updates developer index files for future session context. Use when a coding session is complete, after the human has committed code, or to persist session knowledge for future AI sessions.
mindfold-ai/Trellis 5,124
-
brainstorm
Collaborative requirements discovery session optimized for AI coding workflows. Creates task directories, seeds PRDs, runs codebase research, proposes concrete implementation approaches with trade-offs, and converges on MVP scope through structured Q&A. Use when requirements are unclear, multiple implementation paths exist, trade-offs need evaluation, or a complex feature needs scoping before development.
mindfold-ai/Trellis 5,124
-
break-loop
Deep post-fix bug analysis across five dimensions: root cause categorization, fix failure analysis, prevention mechanisms, systematic expansion, and knowledge capture. Updates .trellis/spec/ guides with lessons learned to prevent recurring bugs. Use when a debugging session completes, after fixing a tricky bug, when the same class of bug keeps recurring, or when you want to capture debugging insights into project documentation.
mindfold-ai/Trellis 5,124
-
parallel
Multi-agent pipeline orchestrator that plans and dispatches parallel development tasks to worktree agents. Reads project context, configures task directories with PRDs and jsonl context files, and launches isolated coding agents. Use when multiple independent features need parallel development, orchestrating worktree agents, or managing multi-agent coding pipelines.
mindfold-ai/Trellis 5,124
-
check
Validates recently written code against project-specific development guidelines from .trellis/spec/. Identifies changed files via git diff, discovers applicable spec modules, runs lint and typecheck, and reports guideline violations. Use when code is written and needs quality verification, to catch context drift during long sessions, or before committing changes.
mindfold-ai/Trellis 5,124
-
record-session
Records completed work progress to .trellis/workspace/ journal files after human testing and commit. Captures session summaries, commit hashes, and updates developer index files for future session context. Use when a coding session is complete, after the human has committed code, or to persist session knowledge for future AI sessions.
mindfold-ai/Trellis 5,124
-
start
Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/. Classifies incoming tasks and routes to brainstorm, direct edit, or task workflow. Use when beginning a new coding session, resuming work, starting a new task, or re-establishing project context.
mindfold-ai/Trellis 5,124
-
onboard
Interactive three-part onboarding for new team members to the Trellis AI-assisted workflow system. Covers core philosophy (AI memory, project-specific knowledge, context drift), system structure and command deep-dives, real-world workflow examples, and guideline customization. Use when a new developer joins the project, someone needs to understand the Trellis workflow, or project guidelines need initial setup.
mindfold-ai/Trellis 5,124
-
break-loop
Deep post-fix bug analysis across five dimensions: root cause categorization, fix failure analysis, prevention mechanisms, systematic expansion, and knowledge capture. Updates .trellis/spec/ guides with lessons learned to prevent recurring bugs. Use when a debugging session completes, after fixing a tricky bug, when the same class of bug keeps recurring, or when you want to capture debugging insights into project documentation.
mindfold-ai/Trellis 5,124
-
record-session
Records completed work progress to .trellis/workspace/ journal files after human testing and commit. Captures session summaries, commit hashes, and updates developer index files for future session context. Use when a coding session is complete, after the human has committed code, or to persist session knowledge for future AI sessions.
mindfold-ai/Trellis 5,124
-
start
Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/. Classifies incoming tasks and routes to brainstorm, direct edit, or task workflow. Use when beginning a new coding session, resuming work, starting a new task, or re-establishing project context.
mindfold-ai/Trellis 5,124