What is modus-angular-implementation-guides?

A planning rule for major Angular and Vite work. An implementation guide is a written plan that explains how a feature will be built before coding starts.

Use it before building complex pages, reusable components, external-service integrations, authentication, routing changes, accessibility work, or other tasks expected to take more than two hours.

It reduces unclear approaches and makes large changes easier to review, follow, and improve after implementation.

modus-angular-implementation-guides — Cursor rule by julianoczkowski

Install

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.

agentmods

npx agentmods add rules/julianoczkowski/create-trimble-app/modus-angular-implementation-guides

Clone the repo

git clone --depth 1 https://github.com/julianoczkowski/create-trimble-app

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 1,491 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.01491
Opus 5	$0.00000	$0.00745
Sonnet 5	$0.00000	$0.00298
Haiku 4.5	$0.00000	$0.00149

Measured 2d ago against content hash 5fc32c032cfc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

modus-angular-implementation-guides 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.

templates/angular/.cursor/rules/modus-angular-implementation-guides.mdc · 302 lines

How it starts

The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implementation Guide Documentation Rules for Angular + 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

Required Implementation Guide Template

# [Feature Name] Implementation Guide

**Date:** YYYY-MM-DD  
**Author:** [Your Name]  
**Status:** [Planning | In Progress | Complete | Archived]

## Overview & Objectives

### Problem Statement

- What problem are we solving?
- Why is this feature needed?
- What are the success criteria?

### Goals & Requirements

- [ ] Functional requirement 1
- [ ] Functional requirement 2
- [ ] Non-functional requirement 1 (performance, accessibility, etc.)

## Technical Architecture

### Component Architecture

- High-level component structure
- Data flow diagrams
- State management approach (signals, services)

### Angular-Specific Patterns

- Standalone components used
- Signal-based state management
- Service patterns
- Routing configuration

### Dependencies & Integrations

- New dependencies required
- External API integrations
- Modus Web Components usage

### File Structure Changes

```text
src/app/
├── components/
│   └── new-component.component.ts
├── pages/
│   └── new-page/
│       └── new-page.component.ts
├── services/
│   └── new-feature.service.ts
└── app.routes.ts

Design System Integration

Modus Components Used

List specific Modus Web Components
Color variables and theming approach
Accessibility considerations

Implementation Plan

Phase 1: Foundation

Task 1
Task 2
Task 3

Phase 2: Core Features

Task 1
Task 2

Phase 3: Polish & Testing

Task 1
Task 2

Testing Strategy

Unit Testing

Components to test
Test scenarios
Mock requirements

Integration Testing

API integration tests
Component interaction tests

Accessibility Testing

WCAG compliance checklist
Screen reader testing
Keyboard navigation testing

Post-Implementation Review

Lessons Learned

[Update this section during/after implementation]

What Went Well

Challenges Encountered

Solutions & Workarounds

Future Improvements

Read the full file on GitHub · 302 lines

Changes

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 · 302 lines · 0 tokens per session scan A 5fc32c032cfc

Subscribe to this mod's changes

modus-angular-implementation-guides is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,491 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning cli modus trimble

modus-angular-implementation-guides