ctx-config
Manage runtime configuration profiles. Use when asked to switch to dev mode, check active profile, toggle verbose logging, or switch to base.
Best use case
ctx-config is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Manage runtime configuration profiles. Use when asked to switch to dev mode, check active profile, toggle verbose logging, or switch to base.
Teams using ctx-config should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ctx-config/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-config Compares
| Feature / Agent | ctx-config | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manage runtime configuration profiles. Use when asked to switch to dev mode, check active profile, toggle verbose logging, or switch to base.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Manage `.ctxrc` configuration profiles (dev vs base). ## When to Use - User says "switch to dev mode" / "switch to dev" - User says "switch to base" / "switch to prod" - User says "what profile am I on?" - User says "toggle verbose logging" - User says "show config status" ## Commands ```bash # Switch to a specific profile ctx config switch dev ctx config switch base # Toggle between profiles (no argument) ctx config switch # Show which profile is active ctx config status ``` ## Profiles | Profile | Description | |---------|---------------------------------------------| | `dev` | Verbose logging, webhook notifications on | | `base` | All defaults, notifications off | Source files (`.ctxrc.base`, `.ctxrc.dev`) are committed to git. The working copy (`.ctxrc`) is gitignored. ## Process 1. Determine which operation the user wants (switch or status) 2. Run the appropriate `ctx config` command 3. Report the result to the user
Related Skills
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
ctx-sanitize-permissions
Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.
ctx-recall
Browse session history. Use when referencing past discussions or finding context from previous work.
ctx-prompt
Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.
ctx-journal-normalize
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
ctx-import-plans
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
ctx-compact
Archive completed tasks and trim context. Use when context files are growing large.
ctx-check-links
Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.
ctx-add-task
Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.
ctx-add-learning
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
ctx-add-decision
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.