Choose the tools for your next task
What are you working on?
Plan a product, build an app, or prepare a pitch. Start with a toolkit or assemble your own from the tools that fit the work.
Claude app · Claude Code CLI · Codex app · Codex CLI
Pick a plan when the trial ends. Cancel any time. Card required.
- Plan
- Research and requirements
- Build
- Implementation and tests
- Present
- Story, slides, and review
Choose a toolkit before each launch. Your coding app does the work; code-config.com prepares the setup.
Choose the work
Turn customer feedback into a product plan.
Bring research, prioritization, and requirements-writing skills into one toolkit. Turn customer feedback into a clear product brief in your coding app.
Decide what to test before you build.
Build a toolkit for customer research, competitor analysis, and experiment design. Give your startup idea a clear set of assumptions to test.
Build the app. Skip the repeated setup.
Choose skills and tools for your stack. Reuse your development setup across projects without copying the same configuration into every repository.
Turn rough notes into a clear presentation.
Assemble tools for storytelling, slide writing, charts, and presentation export. Reuse your presentation workflow in the coding app you already use.
Get the launch materials ready.
Build a toolkit for positioning, landing-page copy, launch emails, and editorial review. Reuse your brand instructions across launch projects.
Get the right tools around the bug.
Assemble a focused toolkit for reproducing bugs, inspecting evidence, and writing regression tests. Keep it ready for the next investigation.
Give every review a consistent starting point.
Reuse your review checklist, testing guidance, and repository conventions in a dedicated toolkit. Give each review a consistent starting point.
Improve your setup
Your first toolkit already has tools in it.
Start with a ready-made toolkit, review its tools, and let your coding agent guide you through setup. Change the toolkit whenever you need to.
Switch coding apps. Keep your toolkit.
Reuse one toolkit across the Claude app, Claude Code CLI, the Codex app, and Codex CLI. Check what each app supports before applying it.
Your toolkit, on every connected computer.
Reuse your toolkit on connected computers. Apply changes on the next launch, see sync status, and set up keys separately on each machine.
Keep your setup. Add what you need.
Bring existing tools into reusable toolkits gradually. Review the changes first; each launch uses its own configuration folder.
A toolkit for each client.
Set a default toolkit for each client's projects. Reuse their tools and instructions without choosing the setup again every time you launch.
Share your team's coding setup.
Share an eligible toolkit with teammates. Everyone keeps their own account and copy, with notifications when the author shares an update.
A toolkit sized to the task.
Choose relevant tools and instructions instead of one giant setup. Understand what a toolkit controls and why token savings depend on the app and task.
The MCP servers your project needs.
Reuse MCP server setup in Claude Code and Codex toolkits. Choose servers by project and configure required keys locally on each computer.
Find useful tools. Skip the repository digging.
Browse individual skills, agents, and MCP servers from GitHub repositories. Check their sources and compatibility, then combine the useful parts.
Publish a toolkit people can add to their account.
Share an eligible toolkit in Community or by an unlisted link. Explain what it includes, keep authorship visible, and tell followers about updates.
Your keys stay out of our cloud.
Store keys on the computer that uses them. See what syncs to your account, what stays on your computer, and what a toolkit you share carries.
Use your coding app
Stop rebuilding your Claude Code setup.
Reuse your Claude Code skills, agents, rules, and settings across projects. Review the configuration before launch instead of rebuilding it by hand.
Your Codex setup, ready for each project.
Reuse Codex skills, instructions, and settings across projects. Review toolkit changes and keep your everyday configuration separate.
Questions
Are these all preinstalled toolkits?
No. The task pages show workflows you can assemble. Your account's starter toolkit and available Community listings are separate; inspect their actual contents before using them.
Can I keep using my existing tools?
Yes. Bring supported tools into a toolkit gradually, or start from a ready-made toolkit and adjust it.
Do I need a different project for every task?
No. Use one project and choose a toolkit for each launch. That choice can differ from the project's default.