Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/julianoczkowski/create-trimble-appWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/julianoczkowski/create-trimble-app/implementation-guides-solidjs)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/implementation-guides-solidjs"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/implementation-guides-solidjs.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02396 |
| Opus 5 | $0.00000 | $0.01198 |
| Sonnet 5 | $0.00000 | $0.00479 |
| Haiku 4.5 | $0.00000 | $0.00240 |
Grade A, and why
implementation-guides-solidjs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
92% identical to implementation-guides-react — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Guide Documentation Rules for SolidJS + Vite
📋 Pre-Development Documentation Requirements
🚨 MANDATORY: Implementation Guide Creation
BEFORE starting ANY major feature development, you MUST:
- Create a comprehensive implementation guide in
/implementation_guides/ - Document the complete approach before writing any code
- Get stakeholder review of the implementation plan
- Update guides with lessons learned during and after implementation
🎯 What Constitutes a "Major Feature"
Always create implementation guides for:
- ✅ New page/view components with complex functionality
- ✅ New reusable component libraries or design system additions
- ✅ Integration with external APIs or services
- ✅ Authentication, authorization, or security features
- ✅ Data management patterns (stores, state management)
- ✅ Routing or navigation changes
- ✅ Performance optimization initiatives
- ✅ Accessibility improvements or compliance work
- ✅ Build process, tooling, or infrastructure changes
- ✅ Any feature requiring more than 2 hours of development time
Skip implementation guides for:
- ❌ Simple bug fixes (< 30 minutes)
- ❌ Minor text or styling tweaks
- ❌ Documentation updates
- ❌ Dependency version updates (unless breaking changes)
📁 Implementation Guide Structure
📍 File Location & Naming
implementation_guides/
├── feature-name-YYYY-MM-DD.md # New feature guides
├── integration-api-name-YYYY-MM-DD.md # API integration guides
├── component-library-YYYY-MM-DD.md # Component development guides
└── performance-optimization-YYYY-MM-DD.md # Performance guides
Naming Convention:
- Use kebab-case for file names
- Include date for chronological tracking
- Be descriptive but concise
- Examples:
user-dashboard-2025-01-15.mdmodus-table-component-2025-01-15.mdauth0-integration-2025-01-15.md
📋 Required Implementation Guide Template
Every implementation guide MUST include these sections:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 445 lines · 0 tokens per session scan A 1835f4f4a62f
implementation-guides-solidjs is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,396 tokens. A static security scan graded it A with 0 findings. It is 92% identical to implementation-guides-react, differing in 42 lines, and is treated as a copy.
Other cursor rules, from other repositories
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
graphql
GraphQL: schema design, resolvers, performance.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.