OpenWriterControle/.opencode/context/development/navigation.md at 9625e43d92cc2ca46dcb70c904a10ecd0d2f2b8e

feat: enhance developer and advanced profiles with UI, development, and system builder context (#148 )

* chore: bump version to v0.8.0

* chore: update version to 0.7.1 instead of 0.8.0

* docs: expand comparison table with Oh My OpenCode and additional features

* backup: development context before reorganization

* refactor(context): reorganize development folder

- Remove 7 duplicate files (ui/design files exist in ui/web/)
- Remove 2 redundant READMEs (use navigation.md instead)
- Move react-patterns.md to frontend/react/
- Create frontend/react/navigation.md
- Update 4 navigation files (development, ui, frontend, frontend/react)
- Update developer profile (4 path changes: ui-styling-standards, design-systems, design-assets, animation-patterns)
- Update 3 core context files (visual-development.md, design-iteration.md, file-locations.md)

Result: 29 context files (down from 36), no duplicates, clean structure

Refs: REORGANIZATION_PLAN.md, REORGANIZATION_SUMMARY.md

* docs(context): add frontend delegation guide

- Create when-to-delegate.md with clear decision criteria
- Decision matrix for when to delegate vs. handle directly
- Common patterns and examples
- Red flags and green flags
- Frontend-specialist capabilities reference
- Update frontend and development navigation files

Helps orchestrators decide when to delegate UI work to frontend-specialist subagent.

* feat: enhance developer and advanced profiles with UI, development, and system builder context

- Developer profile: Add UI/UX patterns, development principles, design systems, React patterns, animation patterns, styling standards, and design assets
- Full profile: Add same UI/development context as developer profile for consistency
- Advanced profile: Add comprehensive system builder context including templates, guides, context system standards, and repository management context
- Update profile descriptions to reflect new capabilities
- All context files verified to exist and are properly referenced

* fix: remove duplicate context entries with incorrect paths

- Remove duplicate design-assets, ui-styling-standards, clean-code, animation-patterns, design-systems, react-patterns, and api-design entries that pointed to wrong paths
- Remove non-existent development-readme and mastra-ai-readme entries
- Keep only correct entries with proper file paths
- All registry paths now validated and correct

---------

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

2026-01-30 22:21:12 +00:00

2.5 KiB

Raw Blame History

Purpose: Software development across all stacks

Structure

development/
├── navigation.md
├── ui-navigation.md           # Specialized
├── backend-navigation.md      # Specialized
├── fullstack-navigation.md    # Specialized
│
├── principles/                # Universal (language-agnostic)
│   ├── navigation.md
│   ├── clean-code.md
│   └── api-design.md
│
├── frameworks/                # Full-stack frameworks
│   ├── navigation.md
│   └── tanstack-start/
│
├── ai/                        # AI & Agents
│   ├── navigation.md
│   └── mastra-ai/
│
├── frontend/                  # Client-side
│   ├── navigation.md
│   ├── when-to-delegate.md    # When to use frontend-specialist
│   └── react/
│       ├── navigation.md
│       └── react-patterns.md
│
├── backend/                   # Server-side (future)
│   ├── navigation.md
│   ├── api-patterns/
│   ├── nodejs/
│   ├── python/
│   └── authentication/
│
├── data/                      # Data layer (future)
│   ├── navigation.md
│   ├── sql-patterns/
│   ├── nosql-patterns/
│   └── orm-patterns/
│
├── integration/               # Connecting systems (future)
│   ├── navigation.md
│   ├── package-management/
│   ├── api-integration/
│   └── third-party-services/
│
└── infrastructure/            # DevOps (future)
    ├── navigation.md
    ├── docker/
    └── ci-cd/

Quick Routes

Task	Path
UI/Frontend	`ui-navigation.md`
When to delegate frontend	`frontend/when-to-delegate.md`
Backend/API	`backend-navigation.md`
Full-stack	`fullstack-navigation.md`
Clean code	`principles/clean-code.md`
API design	`principles/api-design.md`

By Concern

Principles → Universal development practices Frameworks → Full-stack frameworks (Tanstack Start, Next.js) AI → AI frameworks and agent runtimes (MAStra AI) Frontend → React patterns and component design Backend → APIs, Node.js, Python, auth (future) Data → SQL, NoSQL, ORMs (future) Integration → Packages, APIs, services (future) Infrastructure → Docker, CI/CD (future)

Core Standards → ../core/standards/navigation.md
UI Patterns → ../ui/navigation.md

2.5 KiB Raw Blame History

Development Navigation

Structure

Quick Routes

By Concern

Related Context

2.5 KiB

Raw Blame History