ijfw-agents-md

Solid

Maintain canonical AGENTS.md (open spec). Trigger: 'agents.md', 'update AGENTS.md', or auto-fired by ijfw-team after agent generation.

AI & Automation 184 stars 32 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
75
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# IJFW AGENTS.md Manager Maintains a project's `AGENTS.md` per the open spec at https://agents.md/. AGENTS.md is the canonical agent-instructions surface across every IJFW host (Claude, Gemini, Codex, Wayland, Hermes, Cursor, Windsurf, Copilot). Each platform-specific file (`CLAUDE.md`, `GEMINI.md`, `WAYLAND.md`, etc.) is a thin adapter that points here. --- ## When to Invoke - User says: "agents.md", "update AGENTS.md", "regenerate agents file". - Auto-fired by `ijfw-team` after generating agents to `.ijfw/agents/`. - Auto-fired by session-start hooks to refresh memory + agents blocks. - Auto-fired by `ijfw-workflow` at brainstorm-LOCK and plan-LOCK with intent context (v1.4.4 N7). --- ## Marker Block Taxonomy (reserved -- do not break) The file is segmented by four IJFW-managed regions. Content outside markers is user-authored and untouched. | Block | Purpose | |-------------|----------------------------------------------------------| | MEMORY | Pointer to project memory + last handoff summary | | ROUTING | Peer-skill routing rules (workflow, design, etc.) | | AGENTS | Auto-generated agent definitions from `.ijfw/agents/` | | BLACKBOARD | Reserved for Pillar B (multi-CLI orchestration); empty | | DISCIPLINE | Per-domain discipline rules (code \| narrative \| business \| design \| research) | Each block is delimited by `<!-- IJFW-<NAME>-START -->` / `<!-- IJFW-<NAME>-END -->` ...

Details

Author
FerroxLabs
Repository
FerroxLabs/ijfw
Created
1 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category