contract-lookup
Skill2 starsChanged 8 months agoMITView on GitHub
Find which SQWR contracts apply to a given task, feature, or domain. Returns specific rules and numerical thresholds.
In this repository11 other files it gives its agents.
- global/CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- audit-runnerSkill
- auto-fixSkill
- brainstormSkill
- compliance-checkSkill
- monthly-reviewSkill
- new-featureSkill
- pre-deploymentSkill
- project-setupSkill
- risk-scoreSkill
The file
Files
/contract-lookup — Contract Lookup
Usage: /contract-lookup [task or domain description]
Finds the applicable SQWR contracts and specific rules for the task or domain described in $ARGUMENTS.
How to use
Describe what you are building or the domain you are working in:
/contract-lookup user authentication form/contract-lookup payment integration/contract-lookup image gallery with lazy loading/contract-lookup REST API endpoint with rate limiting/contract-lookup database schema migration
Lookup process
- Parse the request: Identify key technical domains in
$ARGUMENTS - Map domains to contracts:
| Domain keyword | Contracts to check |
| form, input, validation | CONTRACT-SECURITY §3, CONTRACT-ACCESSIBILITY §2 |
| password, auth, JWT | CONTRACT-SECURITY §1, CONTRACT-SUPABASE §2 |
| API, endpoint, REST, GraphQL | CONTRACT-API-DESIGN |
| database, schema, migration | CONTRACT-DATABASE-MIGRATIONS, CONTRACT-SUPABASE |
| performance, loading, LCP | CONTRACT-PERFORMANCE, CONTRACT-NEXTJS |
| accessibility, a11y, WCAG | CONTRACT-ACCESSIBILITY |
| TypeScript, types | CONTRACT-TYPESCRIPT |
| test, spec, coverage | CONTRACT-TESTING |
| deploy, CI, CD | CONTRACT-CICD, CONTRACT-VERCEL |
| error, exception | CONTRACT-ERROR-HANDLING |
| log, monitoring | CONTRACT-OBSERVABILITY |
| AI, LLM, prompt | CONTRACT-AI-PROMPTING, CONTRACT-ANTI-HALLUCINATION |
| image, video, media | CONTRACT-PERFORMANCE, CONTRACT-ACCESSIBILITY |
| email, SMTP | CONTRACT-EMAIL |
| SEO, metadata | CONTRACT-SEO |
| i18n, locale, translation | CONTRACT-I18N |
| iOS, Swift | CONTRACT-IOS |
| Android, Kotlin | CONTRACT-ANDROID |
| Python | CONTRACT-PYTHON |
| CONTRACT-PDF-GENERATION | |
| animation, motion | CONTRACT-MOTION-DESIGN |
| analytics, events | CONTRACT-ANALYTICS |
| pricing, subscription | CONTRACT-PRICING |
- Read each relevant contract and extract:
- The specific sections that apply
- The numerical thresholds (these are mandatory, not advisory)
- The source standards (OWASP, WCAG, NIST, etc.)
- Output a summary in this format:
## Applicable contracts for: [task description]
### CONTRACT-X.md — §N [Section name]
Rule: [exact rule with numerical threshold]
Source: [standard]
Why it applies: [reason]
### CONTRACT-Y.md — §M [Section name]
...Source
All contracts: contracts/CONTRACT-*.md
Source philosophy: METHODOLOGY.md — every rule must have a verifiable source with a numerical threshold.
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
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.

