codebase-design

Use when designing or improving a module interface, choosing a seam, reducing shallow modules, making code easier to test, or reviewing architecture for…

Skill by tensology

IndexedMIT★ 17

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/tensology-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.

About

Use when designing or improving a module interface, choosing a seam, reducing shallow modules, making code easier to test, or reviewing architecture for locality, leverage, adapters, and deep-module design.

Use cases: design, testing

Reviews

Write a review

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 designing or improving a module interface, choosing a seam, reducing shallow modules, making code easier to test, or reviewing architecture for locality, leverage, adapters, and deep-module design.
License: MIT
Instructions: 24 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Codebase Design

Use this vocabulary when shaping code so Decisions workflows and future agents talk about architecture consistently.

## Vocabulary

- **Module:** anything with an interface and implementation: function, class, package, or vertical slice.
- **Interface:** everything a caller must know: type shape, invariants, ordering, errors, config, and performance.
- **Implementation:** what sits behind the interface.
- **Depth:** how much behavior sits behind a small interface.
- **Seam:** where behavior can vary without editing the caller.
- **Adapter:** a concrete implementation at a seam.
- **Leverage:** capability gained by callers.
- **Locality:** change and verification concentrated in one place.

## Rules

- Prefer deep modules: small interface, rich implementation.
- Use the deletion test: if removing the module only moves complexity, it was shallow.
- Tests should cross the same interface callers use.
- One adapter means a hypothetical seam. Two adapters means a real seam.
- In Decisions tickets, name modules with project domain terms and record durable decisions in project docs or workflow memory.

From tensology/decisionsai, MIT.

Signals

Stars: 17
Forks: 2
Open issues: 0
Last commit (this folder): Oct 2, 2026 (26 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/tensology/decisionsai
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from tensology

Cite this page

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