agentleFS
kunalsurikunalsuri/ai-fication-kit/.cursor/rules/verify-ai-readiness.mdc

ai-fication-kit / rules

Cursor rule3 starsChanged 4 months agoApache-2.0View on GitHub

Holistic assessment of the AI knowledge layer on a 5-level maturity scale; flags agent-blocking gaps.

The file

We split this verify-ai-readiness.mdc into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Level 0 — Opaque: No agent entry files; agents crawl and guess.

    line 10
  2. Very specific:

    Write ai/analysis/audit-reports/<YYYY-MM-DD>-readiness.md: overall level, per-area table (area · evidence · level), the SINGLE most …

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
verify-ai-readiness.mdc
---
description: Holistic assessment of the AI knowledge layer on a 5-level maturity scale; flags agent-blocking gaps.
alwaysApply: false
---
<!-- Copyright (c) 2026 Kunal Suri (CEA LIST). All rights reserved. -->

Assess how ready this repository is for agentic work. Read-only; output one report.

## The maturity scale
- **Level 0 — Opaque.** No agent entry files; agents crawl and guess.
- **Level 1 — Scaffolded.** Kit installed; maps exist but are placeholders.
- **Level 2 — Drafted.** /cold-start ran; maps populated but `[inferred]`.
- **Level 3 — Verified.** Human audit done: Stability set, core rows `[verified]`.
  *The minimum bar for letting an agent build features.*
- **Level 4 — Maintained.** Feature catalog exists; knowledge updated on merge;
  audits recur; evaluations recorded in ai/lab/.

## Method
Score each: entry files (CLAUDE.md/AGENTS.md), MODULE_MAP coverage & verification
ratio (% rows `[verified]`), FEATURE_MAP/CATALOG coverage, conventions, diagrams,
ai/lab/ activity. Evidence = file contents only; no speculation.

## Output
Write `ai/analysis/audit-reports/<YYYY-MM-DD>-readiness.md`: overall level, per-area
table (area · evidence · level), the SINGLE most valuable next action, and any
agent-blocking gaps (anything that would make a feature build unsafe today).
Tag the report `[inferred]`.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.