Agent skill · AI & Agents

agent-native-architecture

This skill should be used when building AI agents using prompt-native architecture where features are defined in prompts, not code. Use it when creating autonomous agents, designing MCP servers, implementing self-modifying systems, or adopting the "trust the agent's intelligence" philosophy.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill agent-native-architecture-iamladi-cautious-computing-m --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 15 KB
Bundled scripts: none
Path: skills/agent/agent-native-architecture-iamladi-cautious-computing-m/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<essential_principles> ## The Prompt-Native Philosophy Agent native engineering inverts traditional software architecture. Instead of writing code that the agent executes, you define outcomes in prompts and let the agent figure out HOW to achieve them. ### The Foundational Principle **Whatever the user can do, the agent can do. Many things the developer can do, the agent can do.** Don't artificially limit the agent. If a user could read files, write code, browse the web, deploy an app—the agent should be able to do those things too. The agent figures out HOW to achieve an outcome; it doesn't just call your pre-written functions. ### Features Are Prompts Each feature is a prompt that defines an outcome and gives the agent the tools it needs. The agent then figures out how to accomplish it. **Traditional:** Feature = function in codebase that agent calls **Prompt-native:** Feature = prompt defining desired outcome + primitive tools The agent doesn't execute your code. It uses primitives to achieve outcomes you describe. ### Tools Provide Capability, Not Behavior Tools should be primitives that enable capability. The prompt defines what to do with that capability. **Wrong:** `generate

What's inside
Steps it walks through
  1. The Prompt-Native Philosophy
  2. The Foundational Principle
  3. Features Are Prompts
  4. Tools Provide Capability, Not Behavior
  5. The Development Lifecycle
  6. Self-Modification (Advanced)
  7. When NOT to Use This Approach
  8. Architecture Review Checklist (Apply During Design)
  9. Tool Design
  10. Action Parity
  11. UI Integration
  12. Context Injection
  13. Mobile (if applicable)
  14. Domain Knowledge
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the agent-native-architecture skill do?

This skill should be used when building AI agents using prompt-native architecture where features are defined in prompts, not code. Use it when creating autonomous agents, designing MCP servers, implementing self-modifying systems, or adopting the "trust the agent's intelligence" philosophy.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill agent-native-architecture-iamladi-cautious-computing-m --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going