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.
npx agentmods add rules/julianoczkowski/create-trimble-app/development-workflow-solidjsgit 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/development-workflow-solidjs)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/development-workflow-solidjs"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/development-workflow-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.01985 |
| Opus 5 | $0.00000 | $0.00992 |
| Sonnet 5 | $0.00000 | $0.00397 |
| Haiku 4.5 | $0.00000 | $0.00198 |
Grade A, and why
development-workflow-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 2d 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
91% identical to development-workflow-react — 70 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Workflow & Quality Assurance for SolidJS + Vite
🚀 MANDATORY: Always Run Linting Commands During Development
CRITICAL: Before making any code changes, always run these linting commands to ensure design system compliance:
# 🎨 Check for inline styles that should use Tailwind classes
npm run lint:styles
# 🎨 Check for non-Modus colors (hex, RGB, Tailwind colors)
npm run lint:colors
# 🎨 Check for non-Modus icons (Font Awesome, Material Icons, etc.)
npm run lint:icons
# 🎨 Check for semantic HTML elements (h1, section, header, etc.)
npm run lint:semantic
# 🎨 Check for border violations (Tailwind color classes in borders)
npm run lint:borders
# 🔍 Run all linting checks at once
npm run lint:all
📋 Pre-Development Checklist
Before starting any new feature or component:
-
✅ Run Design System Lints:
npm run lint:styles # Check inline styles npm run lint:colors # Check color usage npm run lint:icons # Check icon usage npm run lint:semantic # Check semantic HTML elements npm run lint:borders # Check border violations -
✅ Verify Theme Compatibility:
- Test with all 6 Modus themes (classic/modern, light/dark, connect themes)
- Ensure components work in both light and dark modes
-
✅ Check Component Architecture:
- Use single configurable components (not multiple specific ones)
- Follow Modus Web Components patterns
- Use proper event handling with refs
🔄 Development Workflow
Every time you make changes:
- Make your changes to components/pages
- Run linting commands to catch violations early:
npm run lint:all - Fix any violations before continuing
- Test with Chrome DevTools to validate visual changes
- Commit only when all lints pass
🚨 Common Violations to Watch For
Inline Styles (lint:styles):
// ❌ VIOLATION: Inline styles
style={{ backgroundColor: "var(--modus-wc-color-base-page)" }}
style={{ marginRight: "8px" }}
style={{ color: "var(--modus-wc-color-base-content)" }}
// ✅ CORRECT: Tailwind classes
class="bg-background mr-2 text-foreground"
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.
- 2d ago First seen · 293 lines · 0 tokens per session scan A 4abd223af264
development-workflow-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 1,985 tokens. A static security scan graded it A with 0 findings. It is 91% identical to development-workflow-react, differing in 70 lines, and is treated as a copy.
Other cursor rules, from other repositories
frontend-architecture
Cursor rule "frontend-architecture" from tomasz-tomczyk/crit, covering frontend architecture, two-paradigm page fork, module pattern, shared modules (used by both modes) and code-review modules (used only by code-review mode).
proxy-auth-transport
Every CLI command or browser UI action that calls a crit-web API must work in both modes.
hatch3r-design-system-detection
Mandatory detection of existing design tokens, theme primitives, and component library before AI agents author new UI components.
nuxt-review-bans
🔒 LOCKED — managed by clade Source: rules/modules/framework/nuxt/nuxt-review-bans.md Edit at: $CLADEHOME Local edits will be reverted by the next sync. -->.
hatch3r-ux-states-and-flows
Four-state surface contract (loading/empty/error/partial), user-flow decomposition before implementation, and microcopy + tone discipline for end-user UIs.
hatch3r-accessibility-standards
Accessibility standards covering WCAG 2.2 AA compliance, keyboard navigation, screen readers, and ARIA patterns.