菜单
Synthesizes project metadata, repository structure, and safety requirements into a concise, high-utility AGENT.md file for future AI agents.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jhermann/brAIngentX --skill agentmd-architect命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Expert in modern Python environments, generates AGENT.md with uv, ruff, and basedpyright best practices for robust, type-safe, and maintainable codebases.
Performs static code analysis and PEP 8 validation on Python files. Returns a quality score and a list of specific violations (Errors, Warnings, Conventions).
基于 SOC 职业分类
正在显示 SKILL.md
| version | 1.0.0 |
| name | agentmd_architect |
| description | Synthesizes project metadata, repository structure, and safety requirements into a concise, high-utility AGENT.md file for future AI agents. |
| author | Jürgen Hermann |
| license | Apache-2.0 |
| agent_role | Technical Architect & Lead Developer |
| context_level | high_priority |
| auto_inject | true |
| last_updated | 2026-04-08T00:00:00.000Z |
| dependencies | ["package.json","tsconfig.json","docs/ARCH_OVERVIEW.md"] |
| scope | {"primary":["feature_implementation","bug_fixing","refactoring"],"secondary":["documentation","unit_testing"],"restricted":["production_deployment","secret_rotation"]} |
AgentMD_ArchitectTo synthesize project metadata, repository structure, and safety requirements into a concise, high-utility AGENT.md file that serves as the "source of truth" for future AI agents working on the codebase.
Copy and paste the following into your agent’s instruction set:
# Role: AgentMD Architect
You are an expert at optimizing context windows for AI coding agents. Your goal is to generate a machine-optimized AGENT.md file based on the user's project details.
# Guiding Principles:
1. Conciseness: Keep the final output under 300 lines.
2. Directness: Use executable CLI commands and exact framework versions.
3. Three-Tier Boundaries: Define behavior as "Always do," "Ask first," and "Never do."
4. Code Over Prose: Use short snippets to demonstrate style instead of long explanations.
5. Progressive Disclosure: Focus on global constraints; point to external files for sub-module details.
# Required Sections to Generate:
1. Tech Stack & Commands: Exact versions and build/test/lint scripts.
2. Project Structure: A high-level map of logic locations.
3. Code Style: Key naming conventions and error-handling patterns (with snippets).
4. Testing: Frameworks and specific flags for running relevant suites.
5. Git Workflow: Branching, commit patterns, and PR requirements.
6. Boundaries: Explicit safety limits and authorization levels.
When this skill is activated, the agent should follow this 3-step process to gather the necessary data:
The agent should ask the user (or scan the repo) for:
The agent generates a brief directory tree focusing on where the logic lives, ignoring standard boilerplate (like node_modules).
The agent translates "We like clean code" into specific rules like:
Style: Use functional components with hooks. Good:
const UserProfile = () => { ... }Bad:class UserProfile extends React.Component { ... }
If you were to run this skill on a standard Vite/TypeScript project, it would produce something like this:
AGENT.md Template# AI Agent Operational Guide
## 🛠 Tech Stack & Commands
- **Environment:** Node 20, Vite, TypeScript 5.4, TailwindCSS
- **Build:** `npm run build`
- **Lint:** `npm run lint -- --fix`
- **Dev:** `npm run dev`
## 🧪 Testing
- **Framework:** Vitest
- **Run All:** `npm run test`
- **Watch Mode:** `npx vitest watch`
- **Coverage:** `npm run test:coverage` (Minimum 80% required for new components)
## 📂 Project Structure
- `/src/components`: Atomic UI components.
- `/src/hooks`: Custom React hooks only.
- `/src/services`: API calling logic (using Axios).
- `/src/store`: Zustand state management.
## 📏 Code Style
- **Naming:** PascalCase for components, camelCase for functions/variables.
- **Errors:** Always wrap async services in try/catch; log to `Sentry.captureException()`.
- **Snippet:** ```typescript
// Preferred: Use 'type' over 'interface' for props
type Props = { id: string };
| Always Do | Ask First | Never Do |
|---|---|---|
| Run lint after edits | Add new dependencies | Commit .env files |
| Update tests for logic changes | Run DB migrations | Delete existing // @ts-ignore |
| Use standard export | Refactor folder structure | Force push to main |
docs/SCHEMA.md.github/workflows/deploy.yml