feat: remove skill types and move architecture docs to references

Author: ciro-maciel

.agent/skills/riligar-business-startup/SKILL.md

@@ -1,6 +1,5 @@
 ---
 name: riligar-business-startup
-type: business
 description: Comprehensive startup planning toolkit. Use for business cases, financial projections (3-5 year models), and market opportunity analysis (TAM/SAM/SOM). Covers investor-ready documentation, fundraising strategy, and go-to-market planning.
 ---
 

.agent/skills/riligar-design-system/SKILL.md

@@ -1,6 +1,5 @@
 ---
 name: riligar-design-system
-type: design
 description: Especialista no Sistema Visual da RiLiGar. Use para: (1) Criação de interfaces web e mobile (Light/Dark Mode), (2) Implementação de componentes UI (Mantine Only), (3) Garantir estética minimalista "Content-First", (4) Aplicar tokens de design via Mantine Theme.
 ---
 

.agent/skills/riligar-dev-architecture/SKILL.md

@@ -1,6 +1,5 @@
 ---
 name: riligar-dev-architecture
-type: development
 description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
 ---
 
@@ -12,13 +11,13 @@ description: Architectural decision-making framework. Requirements analysis, tra
 
 **Read ONLY files relevant to the request!** Check the content map, find what you need.
 
-| File                    | Description                              | When to Read                 |
-| ----------------------- | ---------------------------------------- | ---------------------------- |
-| `context-discovery.md`  | Questions to ask, project classification | Starting architecture design |
-| `trade-off-analysis.md` | ADR templates, trade-off framework       | Documenting decisions        |
-| `pattern-selection.md`  | Decision trees, anti-patterns            | Choosing patterns            |
-| `examples.md`           | MVP, SaaS, Enterprise examples           | Reference implementations    |
-| `patterns-reference.md` | Quick lookup for patterns                | Pattern comparison           |
+| File                                | Description                              | When to Read                 |
+| ----------------------------------- | ---------------------------------------- | ---------------------------- |
+| `references/context-discovery.md`   | Questions to ask, project classification | Starting architecture design |
+| `references/trade-off-analysis.md`  | ADR templates, trade-off framework       | Documenting decisions        |
+| `references/pattern-selection.md`   | Decision trees, anti-patterns            | Choosing patterns            |
+| `references/examples.md`            | MVP, SaaS, Enterprise examples           | Reference implementations    |
+| `references/patterns-reference.md`  | Quick lookup for patterns                | Pattern comparison           |
 
 ---
 

…ar-dev-architecture/context-discovery.md …itecture/references/context-discovery.md.agent/skills/riligar-dev-architecture/context-discovery.md renamed to .agent/skills/riligar-dev-architecture/references/context-discovery.md .agent/skills/riligar-dev-architecture/context-discovery.md renamed to .agent/skills/riligar-dev-architecture/references/context-discovery.md

@@ -1,6 +1,5 @@
 ---
 name: riligar-dev-auth-elysia
-type: development
 description: 'Comprehensive guide for integrating the Riligar Auth Elysia SDK into backend servers. Use when a user needs to: (1) Set up a backend auth plugin, (2) Configure Elysia with Riligar Secret Key, (3) Protect API routes or groups, (4) Access authenticated user data in handlers, (5) Perform manual JWT verification.'
 ---
 
@@ -20,13 +19,18 @@ npm install @riligar/auth-elysia
 
 ### 2. Environment Variables
 
-Set up your Secret Key and URLs in your `.env` file.
+Set up your Secret Key and URLs in your environment files.
 
 > [!CAUTION]
 > Backend integration requires the **Secret Key** (`sk_...`). Never share this key or include it in client-side code.
 
 ```bash
-# .env
+# .env.development
+AUTH_API_URL=https://manager.myauth.click
+AUTH_API_SECRET=sk_test_your_secret_key
+AUTH_JWKS_URL=https://manager.myauth.click/.well-known/jwks.json
+
+# .env.production
 AUTH_API_URL=https://manager.myauth.click
 AUTH_API_SECRET=sk_live_your_secret_key
 AUTH_JWKS_URL=https://manager.myauth.click/.well-known/jwks.json

…lls/riligar-dev-architecture/examples.md …-dev-architecture/references/examples.md.agent/skills/riligar-dev-architecture/examples.md renamed to .agent/skills/riligar-dev-architecture/references/examples.md .agent/skills/riligar-dev-architecture/examples.md renamed to .agent/skills/riligar-dev-architecture/references/examples.md

@@ -1,6 +1,5 @@
 ---
 name: riligar-dev-auth-react
-type: development
 description: 'Comprehensive guide for integrating the Riligar Auth React SDK into web applications. Use when a user needs to: (1) Set up authentication from scratch, (2) Configure AuthProvider, (3) Implement route protection, (4) Use auth hooks or pre-built UI components, (5) Handle login/signup/profile/magic links in React.'
 ---
 
@@ -20,13 +19,16 @@ bun add @riligar/auth-react
 
 ### 2. Environment Variables
 
-Set up your Public Key in your `.env.local` file.
+Set up your Public Key in your environment files.
 
 > [!IMPORTANT]
 > Always use the **Public Key** (`pk_...`) in the frontend. Never expose your Secret Key.
 
 ```bash
-# .env.local
+# .env.development
+VITE_AUTH_API_KEY=pk_test_your_public_key
+
+# .env.production
 VITE_AUTH_API_KEY=pk_live_your_public_key
 ```