tiagosilva07

Capture durable knowledge from the current conversation to the lore inbox. Use when decisions are made, bugs are root-caused, patterns are identified, or lessons are learned. Do NOT capture ephemeral task details.

Behavioral guidelines to reduce common LLM coding mistakes. Apply when writing, reviewing, or refactoring code. Covers thinking before coding, simplicity, surgical changes, and goal-driven execution.

Compile all pending lore captures into structured wiki pages. Merges inbox files into cross-linked pages, updates indexes, and commits to git.

Initialize the lore knowledge base and memory system for the current project. Run once per project before using lore-capture or lore-ingest.

Patterns for building reusable, accessible, production-grade React/TypeScript UI components. Use this whenever you create or review a UI component, build a form, design a component API, or work on the frontend — even if accessibility isn't explicitly mentioned. Covers state handling, a11y, responsiveness, and prop design.

Principles and checks for structuring code with clear boundaries, low coupling, and high cohesion. Use this whenever you are designing a new module, refactoring existing code, reviewing structure, deciding where logic should live, or untangling a messy codebase — even if the user doesn't say the words "clean architecture". Applies to Go, React/TypeScript, and C#/.NET.

A go/no-go checklist for shipping code to production. Use this whenever you're about to deploy, finishing a feature, opening a PR for real traffic, or someone asks "is this production-ready". Covers correctness, errors, security, observability, and scale. Applies to Go, React/TypeScript, and C#/.NET.