Fcakyon Claude Codex Settings
fcakyon Claude Codex Settings is a Claude Code plugin for the Build phase that ships 24 battle-tested skills, commands, hooks, agents, and MCP servers for Claude Code and Codex.
by fcakyon · github.com/fcakyon/claude-codex-settings
Bootstrap Claude Code and Codex with a curated daily-driver bundle of skills, hooks, MCP servers, and commands instead of assembling config from scratch.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install fcakyon-claude-codex-settings@fcakyon/claude-codex-settingsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:fcakyon/claude-codex-settings") and the paste-ready config with skillselion.get_install_config("plugin:fcakyon/claude-codex-settings").
What it does
fcakyon Claude Codex Settings is a Claude Code plugin marketplace-style bundle that packages one maintainer’s production Claude Code and Codex setup for daily use. Solo builders install it to skip months of tuning—skills, slash commands, hooks, subagents, and MCP servers arrive pre-wired for workflows from frontend and Next.js work through Azure, Cloudflare, Hetzner, MongoDB, Lighthouse, and academic citation flows. Because the collection spans review, testing, deploy, and content tasks, it behaves as journey-wide agent configuration even though Skillselion shelves it under build agent-tooling as the first place you attach tooling. Intermediate users benefit most: you still own your repos and secrets, but you inherit opinionated guardrails. It is a config corpus and plugin set, not a hosted product—pair it with your own CLAUDE.md and project rules.
Highlights
- 24 plugins in one repository: skills, commands, hooks, agents, and MCP servers
- Battle-tested personal defaults for Claude Code and OpenAI Codex side by side
- Coverage spans code review, deploy, browser testing, docs, and cloud targets
- Marketplace-to-plugin style packaging for repeatable agent environments
- Methodology-first patterns (e.g. architecture review, simplifier, commit flows) ready to invoke
Why builders use it
Piecing together reliable Claude Code hooks, MCP servers, and skills from scattered repos wastes days before you ship anything.
After install, Claude Code and Codex share a consistent, maintainer-tested plugin stack you can extend per project.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 575 stars, 0 votes.
FAQ
Who is fcakyon Claude Codex Settings for?
It is for solo builders using Claude Code and/or Codex who want a proven all-in-one plugin stack instead of hunting community skills one at a time.
When should I use fcakyon Claude Codex Settings?
Use it when you start a new machine or repo and need commands, hooks, MCP, and review workflows active on day one across build and ship work.
How do I add fcakyon Claude Codex Settings to my agent?
Install plugins from the fcakyon/claude-codex-settings repository via Claude Code marketplace or plugin add, then trim or enable only the 24 bundled pieces you need.
Comments
Share how you use fcakyon-claude-codex-settings, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.