Skip to content
Agentmart
Submit a tool

codebase-design

Use when a module boundary, interface, domain model, or architecture change needs a durable design decision before implementation.

Skill by Rafcin

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/rafcin-codebase-design

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when a module boundary, interface, domain model, or architecture change needs a durable design decision before implementation.

Use cases: design, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/codebase-design

What's inside

Skill name
codebase-design
Description
Use when a module boundary, interface, domain model, or architecture change needs a durable design decision before implementation.
License
MIT
Instructions
21 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Codebase Design

Design deep modules: concentrate behavior behind a small, testable interface at a clean seam.

## Entry conditions

Use for a new or changed module, public contract, domain model, integration seam, or architecture decision. Read callers, tests, and local vocabulary before naming the seam.

## Scope limit

Choose the smallest interface that gives callers leverage and keeps knowledge local. Do not redesign unrelated modules, mistake a directory for a boundary, or invent abstraction before a concrete behavior and caller need justify it.

## Exit evidence

State the module responsibility, interface, invariants and error behavior, owning files, adapters or external boundaries, public test seam, compatibility decision, and rejected alternative when it affected the choice.

## Next gate

Use `plan` for multi-step, delegated, persistent, or risky work. Otherwise hand the agreed seam to `tdd` and `implement` through the declared OMCS route.

From Rafcin/oh-my-codex-slim, MIT.

More from Rafcin/oh-my-codex-slim

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 26, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Rafcin

Cite this page

codebase-design skill. Agent Mart. https://agentmart.dev/skills/rafcin-codebase-design (last updated 2026-10-24)