Datadog Data Source Generator
DataDog/terraform-provider-datadog
Generates a Datadog Terraform provider data source from an OpenAPI operation with tfgen and opens a review-ready GitHub PR with a risk scan and testing guide.
Greenfield architecture design: map functionality flows, draw components, design APIs, classify dependencies, plan observability.
Install Architecture
$ npx skills add romiluz13/cc10x --skill architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install romiluz13/cc10x architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/cc10x/skills/architecture .claude/skills/architecture && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "architecture" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/architecture into .claude/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add romiluz13/cc10x --skill architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install romiluz13/cc10x architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/cc10x/skills/architecture .agents/skills/architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "architecture" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/architecture into .agents/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add romiluz13/cc10x --skill architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install romiluz13/cc10x architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/cc10x/skills/architecture .cursor/skills/architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "architecture" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/architecture into .cursor/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/romiluz13/cc10x.git --path plugins/cc10x/skills/architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add romiluz13/cc10x --skill architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install romiluz13/cc10x architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/cc10x/skills/architecture .gemini/skills/architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "architecture" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/architecture into .gemini/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install romiluz13/cc10x architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add romiluz13/cc10x --skill architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/cc10x/skills/architecture .github/skills/architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "architecture" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/architecture into .github/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add romiluz13/cc10x --skill architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install romiluz13/cc10x architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/cc10x/skills/architecture .opencode/skills/architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "architecture" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/architecture into .opencode/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
architecture- GitHub stars
- 164
- Token cost
- ~1.7k tokens
- SKILL.md length
- 778 words
- Files
- 1
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- MIT
At a glance
Greenfield architecture design: map functionality flows, draw components, design APIs, classify dependencies, plan observability.
- Works in 3 steps: Map Functionality Flows → Map to Architecture → Design Components
- Tasks that involve Observability
- SKILL.md covers Intake Routing, Functionality-First Design…, Architecture Views and LSP-Powered Architecture…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Architecture is an agent skill from romiluz13/cc10x. Greenfield architecture design: map functionality flows, draw components, design APIs, classify dependencies, plan observability. For multi-component, API, schema, auth, or integration-heavy work. For retrofitting existing code, use codebase-hygiene instead.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Observability and OpenAPI specifications. The repository describes itself as: The Loop Engine for Claude Code — engineer the loop, not the prompt. 1 router · 9 agents · 16 skills · 4 workflows. Fail-closed gates, test honesty, anti-anchored review. The licence is MIT.
When your agent uses it
- Tasks that involve Observability
- Tasks that involve OpenAPI specifications
Example prompts
- “/architecture”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, Glob, LSP, Bash
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 891acf0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobLSPBash
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Architecture loads about 1.7k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 778 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Grep, Glob, LSP, Bash
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from romiluz13/cc10x at commit 891acf0, republished under its MIT licence (© romiluz13). 778 words, ~1,742 tokens.
Download SKILL.mdSave it as
.claude/skills/architecture/SKILL.md (or your agent's skills folder).- name
- architecture
- description
- Greenfield architecture design: map functionality flows, draw components, design APIs, classify dependencies, plan observability. For multi-component, API, schema, auth, or integration-heavy work. For retrofitting existing code, use codebase-hygiene instead.
- allowed-tools
- Read, Grep, Glob, LSP, Bash
- user-invocable
- false
Architecture
Design systems from scratch: map flows, then draw components. For retrofitting existing code, use codebase-hygiene instead.
Intake Routing
| Request type | Use |
|---|---|
| New system/major feature (greenfield) | This skill |
| Existing code with shallow modules | codebase-hygiene |
| Multi-component integration | This skill |
| Single-component refactor | planning + building |
Functionality-First Design Process
Phase 1: Map Functionality Flows
Map every user flow end-to-end before designing any component:
Flow: [name]
1. [step] → [what the system does] → [what the user sees]
2. [step] → [what the system does] → [what the user sees]
Error paths:
- [error] → [system response] → [user sees]Every flow must have its error paths mapped. Unmapped error paths become unmapped components.
Phase 2: Map to Architecture
Translate flows into components:
- Each flow step maps to one or more components
- Each error path maps to a component's error handling
- Data crossings between components become interfaces
Phase 3: Design Components
For each component:
- Interface: what it receives and returns (the contract)
- Responsibility: what it does (one sentence)
- Dependencies: what it needs (other components, external services)
- State: what it remembers (if anything)
- Error handling: what can go wrong and what it does about it
Before finalizing any component boundary, apply the Deletion Test and Two-Adapter Rule as defined in cc10x:codebase-design. A component that fails the deletion test (complexity vanishes if deleted) or fails the two-adapter rule (it is a port with only one adapter — an ordinary caller or test exercising the interface is not an adapter) is not a real boundary yet — fold it into its caller or defer the split until a second concrete need appears.
Architecture Views
System Context (C4 Level 1)
Box diagram: your system + external systems it talks to. One paragraph per external system: what it provides, what you depend on.
Container View (C4 Level 2)
Internal boxes: web app, API, database, queue, worker. Arrows show data flow. One paragraph per container: technology choice, responsibility.
Component View (C4 Level 3)
Inside each container: the modules/classes. Arrows show call relationships. This is what the builder will implement.
LSP-Powered Architecture Analysis
Use LSP to understand existing architecture before designing new:
- Go to Definition on key functions to trace the call graph
- Find References to understand blast radius of existing interfaces
- Go to Type Definition to understand data models
- Incoming/Outgoing Calls to map the dependency graph
API Design (Functionality-Aligned)
Design APIs from the flow, not from the data model:
- What does the user need to do? (action, not resource)
- What's the minimal interface that enables it? (fewest endpoints/parameters)
- What's the error contract? (every error case from the flow mapping)
- What's the type contract? (input/output types, not just shapes)
// Good: functionality-aligned
POST /orders/{id}/cancel → { status, cancelledAt }
// Bad: data-model-aligned
PUT /orders/{id} → { ..., status: "cancelled", ... }Integration Patterns
For each integration:
| Field | Value |
|---|---|
| System | [name] |
| Protocol | [HTTP/gRPC/CLI/message queue] |
| Direction | [we call them / they call us / both] |
| Contract | [request/response schema or event schema] |
| Failure mode | [what happens when it's down] |
| Retry policy | [retries, backoff, circuit breaker] |
Show full SKILL.md (337 more words)Show less
Dependency Classification
| Class | Meaning | Example |
|---|---|---|
| Owned | We control the code and deploy it | Internal service |
| Wrapped | We depend on it but wrap it in our interface | Third-party SDK behind adapter |
| Consumed | We depend on it directly, no wrapper | External API called directly |
| Infra | Platform-level dependency | Database, message queue |
Wrapped dependencies can be swapped. Consumed dependencies cannot. Track which is which — it determines your coupling risk.
Observability Design
For each component:
- Logging: what to log (not "everything" — specific events)
- Metrics: what to track (business-relevant, not infra noise)
- Tracing: what to trace (cross-component flows, not every function call)
- Alerting: when to alert (user-visible impact, not internal noise)
Architecture Vocabulary
The deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality, deletion test, two-adapter rule) is defined in cc10x:codebase-design. Use those terms exactly.
Three extra terms specific to greenfield architecture (not in codebase-design):
- Concealed complexity — work done behind a simple interface. The goal of deep modules.
- Temporal coupling — caller must know the order of operations. Design defect — remove or document explicitly.
- Leaky abstraction — interface exposes internal details callers must know. Design defect — fix the interface.
Before finalizing any component boundary, apply the Deletion Test and Two-Adapter Rule as defined in cc10x:codebase-design. A component that fails the deletion test (complexity vanishes if deleted) or fails the two-adapter rule (it is a port with only one adapter — an ordinary caller or test exercising the interface is not an adapter) is not a real boundary yet — fold it into its caller or defer the split until a second concrete need appears.
Design It Twice
When a module's interface is non-trivial, design it twice:
- First design: the obvious approach. Write it out fully.
- Second design: a different approach (not a refinement of the first).
Compare both. The first design is usually shallow — it mirrors the implementation. The second design reveals what the interface should hide. Use the better one, or a hybrid.
Why: One-pass interfaces optimize for the implementer. Two-pass interfaces optimize for the caller.
Decision Framework
For architectural decisions with material trade-offs:
### Decision: [Title]
**Context:** [why this decision is needed]
**Options:** [2-3 alternatives with trade-offs]
**Decision:** [what was chosen]
**Rejected:** [what was not chosen and why]
**Consequences:** [what this enables and prevents]
**Reversibility:** [reversible or irreversible — irreversible decisions need more evidence]© romiluz13, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/cc10x/skills/architecture of romiluz13/cc10x.
Open the folder on GitHubat commit 891acf0
Compare with similar skills
Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Architecture this skillromiluz13/cc10x | 164 | — | ~1.7k | Automated safety check: Notes | MIT | |
| Datadog Data Source GeneratorDataDog/terraform-provider-datadog | 468 | — | ~2.7k | Automated safety check: Pass | MPL-2.0 | |
| Distributed Tracingwshobson/agents | 40k | 11 repos | ~527 | Automated safety check: Pass | MIT | |
| Aliyun Swas Managecinience/alicloud-skills | 397 | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| OmniRoute Health Monitoringdiegosouzapw/OmniRoute | 74k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Migrate Dotnet9 To Dotnet10dotnet/skills | 5.6k | 2 repos | ~4.8k | Automated safety check: Pass | MIT |
Similar skills
- Official
Distributed Tracing
wshobson/agents
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks.
Aliyun Swas Manage
cinience/alicloud-skills
A skill your agent uses when managing Alibaba Cloud Simple Application Server (SWAS OpenAPI 2020-06-01) resources end-to-end, including querying instances, starting/stopping/rebooting, executing…
OmniRoute Health Monitoring
diegosouzapw/OmniRoute
Checks the health of an OmniRoute gateway: provider circuit breakers, latency percentiles, budget guard alerts, connection cooldowns and model lockouts.
- Official
Migrate Dotnet9 To Dotnet10
dotnet/skills
Migrate a .NET 9 project or solution to .NET 10 and resolve all breaking changes.
Workers Best Practices
hodgef/apiker
Reviews and authors Cloudflare Workers code against production best practices.
More from romiluz13/cc10x
All 22 skills in this repoDiff Driven Docs
romiluz13/cc10x
A skill your agent uses when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation.
Cc10x Guide
romiluz13/cc10x
Answers questions about cc10x itself — what it is, how to install and configure it, how the router, workflows, memory, and hooks operate, and how to troubleshoot.
Cc10x Router
romiluz13/cc10x
THE ONLY ENTRY POINT FOR CC10X. An agent skill from romiluz13/cc10x.
Codebase Design
romiluz13/cc10x
Canonical deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) for designing a module's shape — a lot of behaviour behind a small interface at a clean seam, testable…
MCP CLI
romiluz13/cc10x
A skill your agent uses when you need a one-off MCP server capability during research or debugging without permanently mounting it as a context-polluting integration.
Resolving Merge Conflicts
romiluz13/cc10x
A skill your agent uses when a git merge or rebase reports conflicts and the operation is in progress.
Related
Categories
Questions about Architecture
What does Architecture do?
Greenfield architecture design: map functionality flows, draw components, design APIs, classify dependencies, plan observability. Architecture is an agent skill from romiluz13/cc10x. Greenfield architecture design: map functionality flows, draw components, design APIs, classify dependencies, plan observability.
When should I use Architecture?
Architecture fits situations like: tasks that involve Observability; tasks that involve OpenAPI specifications.
How do I install Architecture in Claude Code?
Run `npx skills add romiluz13/cc10x --skill architecture -a claude-code`. Or copy the skill folder (plugins/cc10x/skills/architecture in romiluz13/cc10x) into .claude/skills/architecture in your project. Claude Code loads it when a task matches its description.
How do I install Architecture in Codex?
Run `npx skills add romiluz13/cc10x --skill architecture -a codex`. Or copy the skill folder (plugins/cc10x/skills/architecture in romiluz13/cc10x) into .agents/skills/architecture in your project. Codex loads it when a task matches its description.
Can I use Architecture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add romiluz13/cc10x --skill architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture, .gemini/skills/architecture, .github/skills/architecture and .opencode/skills/architecture in your project.
What does Architecture need to run?
SKILL.md names no scripts, command-line tools or credentials: Architecture is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, LSP, Bash.
Does Architecture access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Architecture safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Architecture use?
Architecture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Architecture use?
About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Architecture?
Skills that share tags, products or a category with Architecture: Datadog Data Source Generator (DataDog/terraform-provider-datadog, 468 stars), Distributed Tracing (wshobson/agents, 40k stars), Aliyun Swas Manage (cinience/alicloud-skills, 397 stars) and OmniRoute Health Monitoring (diegosouzapw/OmniRoute, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Architecture?
romiluz13 (a GitHub user) maintains it in romiluz13/cc10x, which has 164 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on September 30, 2026.
Source: romiluz13/cc10x on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.