tribunal-kit 2.4.4 → 2.4.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.agent/skills/appflow-wireframe/SKILL.md +72 -0
- package/.agent/skills/frontend-design/SKILL.md +6 -1
- package/.agent/skills/mobile-design/SKILL.md +5 -0
- package/.agent/skills/nextjs-react-expert/SKILL.md +4 -3
- package/.agent/skills/react-specialist/SKILL.md +4 -3
- package/.agent/skills/tailwind-patterns/SKILL.md +5 -0
- package/.agent/skills/ui-ux-pro-max/SKILL.md +1 -0
- package/.agent/skills/vue-expert/SKILL.md +4 -3
- package/README.md +161 -191
- package/package.json +1 -1
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: appflow-wireframe
|
|
3
|
+
description: Skill for the planner agent to generate deterministic application flows (Mermaid) and structural UI wireframes (Pseudo-XML) prior to code execution.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Appflow & Wireframing Skill
|
|
7
|
+
|
|
8
|
+
This skill empowers the planner agent to outline precise user journeys and screen layouts directly in `PLAN-{slug}.md` files. The output must be perfectly readable by humans and easily parsed by downstream code generation agents (like `frontend-specialist`).
|
|
9
|
+
|
|
10
|
+
## Phase 1: App Flow Mapping (Mermaid.js)
|
|
11
|
+
|
|
12
|
+
Before creating wireframes, you must map the logical user journey using a Mermaid.js flowchart.
|
|
13
|
+
|
|
14
|
+
### Rules for Flows:
|
|
15
|
+
- Use `mermaid` blocks with `flowchart TD` (Top-to-Down) or `LR` (Left-to-Right).
|
|
16
|
+
- Focus strictly on state transitions, conditional logic, auth barriers, and API boundaries.
|
|
17
|
+
- Label all decision edges clearly.
|
|
18
|
+
|
|
19
|
+
**Example:**
|
|
20
|
+
```mermaid
|
|
21
|
+
flowchart TD
|
|
22
|
+
Start([User visits /checkout]) --> Auth{Is Logged In?}
|
|
23
|
+
Auth -- No --> Redirect[Send to /login?return=/checkout]
|
|
24
|
+
Auth -- Yes --> Validate{Cart Not Empty?}
|
|
25
|
+
Validate -- No --> ShowEmpty[Render EmptyCart component]
|
|
26
|
+
Validate -- Yes --> ShowCheckout[Render CheckoutLayout]
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
## Phase 2: Semantic Wireframing (Pseudo-XML) & UI Accuracy
|
|
30
|
+
|
|
31
|
+
For mapping UI elements, NEVER use vague bullet points or basic ASCII art. You must use the **Tribunal Structural XML** format. This enforces a component-thinking mindset and provides 1:1 structural intent for the frontend agent.
|
|
32
|
+
|
|
33
|
+
### Rules for UI Accuracy & Tokens:
|
|
34
|
+
To ensure the frontend agent translates the wireframe with pixel-perfect accuracy, you must use explicit spacing, typography, and layout generic tokens (based on a 4px grid) rather than vague words like "large" or "small".
|
|
35
|
+
|
|
36
|
+
- Use PascalCase for components (`<Sidebar>`, `<DataGrid>`, `<MetricCard>`).
|
|
37
|
+
- Define exact layout constraints: `layout="flex-col"`, `flex="1"`, `items="center"`, `justify="between"`.
|
|
38
|
+
- Define spacing using standard numeric scales (1 = 4px): `p="4"`, `gap="2"`, `m="8"`.
|
|
39
|
+
- Define typography explicit roles: `text="xs | sm | base | lg | xl | 2xl"`, `font="bold"`, `text-color="muted"`.
|
|
40
|
+
- Define explicit widths/heights: `w="full"`, `max-w="7xl"`, `h="100vh"`.
|
|
41
|
+
- Provide responsive breakpoints explicitly: `<Grid cols="1" md-cols="3">`.
|
|
42
|
+
|
|
43
|
+
**Example:**
|
|
44
|
+
```xml
|
|
45
|
+
<Screen name="Checkout" layout="flex-row" max-w="7xl" mx="auto" p="4" md-p="8">
|
|
46
|
+
<MainColumn layout="flex-col" gap="8" flex="1">
|
|
47
|
+
<Section title="Shipping Details" text="xl" font="semibold">
|
|
48
|
+
<AddressForm fields="Name, Street, City, Zip" gap="4" />
|
|
49
|
+
</Section>
|
|
50
|
+
<Section title="Payment Method" text="xl" font="semibold">
|
|
51
|
+
<PaymentElement provider="Stripe" p="4" border="1" radius="md" />
|
|
52
|
+
</Section>
|
|
53
|
+
</MainColumn>
|
|
54
|
+
|
|
55
|
+
<SidebarColumn layout="sticky" w="full" md-w="96" p="6" bg="surface-variant" radius="lg">
|
|
56
|
+
<OrderSummary layout="flex-col" gap="4">
|
|
57
|
+
<CartList items="[CartContext]" />
|
|
58
|
+
<Divider />
|
|
59
|
+
<Subtotal layout="flex-row" justify="between" text="sm" text-color="muted" />
|
|
60
|
+
<Tax calculation="dynamic" layout="flex-row" justify="between" text="sm" text-color="muted" />
|
|
61
|
+
<Divider />
|
|
62
|
+
<Total layout="flex-row" justify="between" text="lg" font="bold" />
|
|
63
|
+
<Button action="submitCheckout" variant="primary" w="full" py="3" radius="md">Pay Now</Button>
|
|
64
|
+
</OrderSummary>
|
|
65
|
+
</SidebarColumn>
|
|
66
|
+
</Screen>
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
## Execution Checklist for the Planner:
|
|
70
|
+
- [ ] Has the logical flow been verified in the Mermaid graph?
|
|
71
|
+
- [ ] Does every screen mentioned in the flow have a corresponding `<Screen>` XML wireframe?
|
|
72
|
+
- [ ] Are the wireframe nodes purely structural (no hallucinated styles)?
|
|
@@ -162,7 +162,12 @@ All spacing and sizing in multiples of 8:
|
|
|
162
162
|
└── Adjust based on content density
|
|
163
163
|
```
|
|
164
164
|
|
|
165
|
-
### Key Sizing Principles
|
|
165
|
+
### Key Sizing Principles & UI Building Accuracy
|
|
166
|
+
|
|
167
|
+
To guarantee pixel-perfect accuracy, you must enforce explicit building rules when passing designs to code:
|
|
168
|
+
1. **Never Hallucinate Spacing:** Use exact numeric styling scales (e.g., a 4px grid: `p-4`, `gap-8`, `m-2`). Do NOT use vague terms like "large padding".
|
|
169
|
+
2. **Explicit Layout Boundaries:** Always define `flex`, `grid`, and strict alignment. Never rely on browser auto-margins to guess structure.
|
|
170
|
+
3. **Dimensions:** Explicitly define bounding boxes where applicable (`w-full`, `max-w-7xl`).
|
|
166
171
|
|
|
167
172
|
| Element | Consideration |
|
|
168
173
|
|---------|---------------|
|
|
@@ -113,6 +113,11 @@ Touch screens are wildly imprecise.
|
|
|
113
113
|
|
|
114
114
|
---
|
|
115
115
|
|
|
116
|
+
## 📏 UI Building Accuracy
|
|
117
|
+
|
|
118
|
+
- **Mathematical Layouts:** Mobile layouts require mathematical precision to prevent layout shifts. You MUST use exact spacing multiples (e.g., 4px/8px grids).
|
|
119
|
+
- **Strict Containers:** Explicitly define `flex-1`, `align-items`, and `justify-content` on every view layer. Never let RN guess the intrinsic size.
|
|
120
|
+
|
|
116
121
|
## ⚡ Performance Extremis (Quick Reference)
|
|
117
122
|
|
|
118
123
|
### 120Hz Animation Mandate
|
|
@@ -184,9 +184,10 @@ Do not mark status as VERIFIED until concrete terminal evidence is provided.
|
|
|
184
184
|
|
|
185
185
|
### ❌ Forbidden AI Tropes in Next.js/React
|
|
186
186
|
|
|
187
|
-
1.
|
|
188
|
-
2. **`
|
|
189
|
-
3.
|
|
187
|
+
1. **Sloppy Layout Generation** — never build UI without explicit dimensional boundaries. You MUST apply strict numeric design tokens (e.g. 4px grid spacing) and explicit flex/grid layouts.
|
|
188
|
+
2. **`"use client"` on everything** — do not convert Server Components to Client unless interaction/state is strictly required.
|
|
189
|
+
3. **`getServerSideProps` in App Router** — never hallucinate legacy Pages router data fetching in an App Router context.
|
|
190
|
+
4. **Unnecessary `useEffect` fetching** — always prefer Server Components or SWR/React Query for data fetching.
|
|
190
191
|
4. **Vercel clones** — do not default to generic black/white Vercel aesthetics unless instructed.
|
|
191
192
|
5. **Missing `key` in maps** — always provide a unique, stable key. No using iteration index as the key.
|
|
192
193
|
|
|
@@ -83,9 +83,10 @@ Do not mark status as VERIFIED until concrete terminal evidence is provided.
|
|
|
83
83
|
**Active reviewers: `logic` · `security` · `frontend` · `type-safety`**
|
|
84
84
|
|
|
85
85
|
### ❌ Forbidden AI Tropes in React
|
|
86
|
-
1. **
|
|
87
|
-
2. **
|
|
88
|
-
3. **
|
|
86
|
+
1. **Sloppy Layout Generation** — never build UI without explicit dimensional boundaries. You MUST apply strict numeric design tokens (e.g. 4px grid spacing) and explicit flex/grid layouts.
|
|
87
|
+
2. **Unnecessary `useEffect` Data Fetching** — never fetch raw data inside a `useEffect` if a framework pattern (Server Components, SWR, React Query) is available.
|
|
88
|
+
3. **Missing `key` in maps** — always provide a unique, stable key. No using iteration index as the key.
|
|
89
|
+
4. **Prop Drilling Nightmare** — avoid passing props more than 3 levels deep; use Context or atomic stores (Zustand) instead.
|
|
89
90
|
4. **Over-Memoization** — do not slap `useMemo`/`useCallback` on everything prematurely. Only use it when profiling proves a performance bottleneck.
|
|
90
91
|
5. **Class Components** — never hallucinate class `extends React.Component` or lifecycle methods (`componentDidMount`) in a modern React 18+ app unless explicitly requested for legacy migration.
|
|
91
92
|
|
|
@@ -155,6 +155,11 @@ Do not rely on Javascript to toggle simple dark modes if it can be avoided. Medi
|
|
|
155
155
|
|
|
156
156
|
---
|
|
157
157
|
|
|
158
|
+
## UI Building Accuracy (MANDATORY)
|
|
159
|
+
- **Mathematical Spacing:** Tailwind is a constraint system. You MUST use exact 4px grid steps (`p-4`, `gap-6`, `my-2`) to implement UI. Never guess spacing.
|
|
160
|
+
- **Explicit Layouts:** Every container must have explicit layout boundaries (`flex items-center justify-between` or `grid cols-3 gap-4`).
|
|
161
|
+
- **Boundaries:** Define constraints heavily (`w-full`, `max-w-screen-xl`, `overflow-hidden`).
|
|
162
|
+
|
|
158
163
|
## Performance Rules
|
|
159
164
|
- **Layer Splitting:** `@layer components` and `@layer utilities` prevent specificity issues and allow Tailwind's engine to order CSS correctly.
|
|
160
165
|
- **Do not install plugins without measuring:** Heavy plugins (like unpruned icon libraries) destroy CSS parsing times.
|
|
@@ -36,6 +36,7 @@ Focus on:
|
|
|
36
36
|
- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
|
|
37
37
|
- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
|
|
38
38
|
- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
|
|
39
|
+
- **UI Building Accuracy (MANDATORY)**: You must translate layouts with mathematical precision using strict numeric tokens (4px grid). Every layout must have explicitly defined `flex`/`grid` containers, alignment boundaries, and exact spacing. No vague "auto" spacing unless mathematically intended.
|
|
39
40
|
- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
|
|
40
41
|
|
|
41
42
|
**NEVER** use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
|
|
@@ -100,9 +100,10 @@ Do not mark status as VERIFIED until concrete terminal evidence is provided.
|
|
|
100
100
|
**Active reviewers: `logic` · `security` · `frontend` · `type-safety`**
|
|
101
101
|
|
|
102
102
|
### ❌ Forbidden AI Tropes in Vue
|
|
103
|
-
1. **
|
|
104
|
-
2. **
|
|
105
|
-
3. **
|
|
103
|
+
1. **Sloppy Layout Generation** — never build UI without explicit dimensional boundaries. You MUST apply strict numeric design tokens (e.g. 4px grid spacing) and explicit flex/grid layouts.
|
|
104
|
+
2. **Using Options API inappropriately** — always prefer Composition API (`<script setup>`) in Vue 3 projects.
|
|
105
|
+
3. **Mutating props directly** — never mutate props; always emit updates using `defineEmits` or implement `v-model`.
|
|
106
|
+
4. **Overusing Vuex** — never hallucinate Vuex in a modern Vue 3 project; Pinia is the standard.
|
|
106
107
|
4. **Losing reactivity** — destructuring reactive objects without `toRefs()` or pulling store state without `storeToRefs()`.
|
|
107
108
|
5. **Missing `key` in `v-for`** — always provide a unique, stable key. No using iteration index as the key.
|
|
108
109
|
|
package/README.md
CHANGED
|
@@ -1,191 +1,161 @@
|
|
|
1
|
-
<div align="center">
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
</
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
.
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
<
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
|
101
|
-
|
|
|
102
|
-
|
|
|
103
|
-
|
|
104
|
-
</
|
|
105
|
-
|
|
106
|
-
<
|
|
107
|
-
<
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
|
116
|
-
|
|
|
117
|
-
|
|
|
118
|
-
|
|
|
119
|
-
|
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
<
|
|
125
|
-
<
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
|
130
|
-
|
|
|
131
|
-
|
|
|
132
|
-
|
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
tribunal-kit status # Check installation status
|
|
163
|
-
```
|
|
164
|
-
|
|
165
|
-
---
|
|
166
|
-
|
|
167
|
-
## 🧰 Utility Scripts *(Post-install)*
|
|
168
|
-
|
|
169
|
-
```bash
|
|
170
|
-
python .agent/scripts/checklist.py . # 📋 Pre-commit audit
|
|
171
|
-
python .agent/scripts/verify_all.py # 🚀 Pre-deploy full suite
|
|
172
|
-
python .agent/scripts/auto_preview.py start # 🌍 Start dev server
|
|
173
|
-
python .agent/scripts/session_manager.py save "note" # 💾 Save session state
|
|
174
|
-
```
|
|
175
|
-
|
|
176
|
-
---
|
|
177
|
-
|
|
178
|
-
## 🤝 Compatible IDEs
|
|
179
|
-
|
|
180
|
-
| IDE | Support Level |
|
|
181
|
-
|---|---|
|
|
182
|
-
| **Cursor** | ✅ Reads `.agent/` automatically |
|
|
183
|
-
| **Windsurf** | ✅ Reads `.agent/` automatically |
|
|
184
|
-
| **Antigravity** | ✅ Native `.agent/` support |
|
|
185
|
-
| **GitHub Copilot** | ✅ Manual setup: Copy `GEMINI.md` to `.github/copilot-instructions.md` |
|
|
186
|
-
|
|
187
|
-
<br>
|
|
188
|
-
|
|
189
|
-
<div align="center">
|
|
190
|
-
<sub>Built with ❤️ for safer, hallucination-free AI coding.</sub>
|
|
191
|
-
</div>
|
|
1
|
+
<div align="center">
|
|
2
|
+
<picture>
|
|
3
|
+
<img src="./docs/image.png" alt="Tribunal Kit Logo" width="300">
|
|
4
|
+
</picture>
|
|
5
|
+
|
|
6
|
+
<h1><b>TRIBUNAL—KIT</b></h1>
|
|
7
|
+
|
|
8
|
+
<p><code>< ZERO_HALLUCINATION_PROTOCOL /></code></p>
|
|
9
|
+
|
|
10
|
+
<p>
|
|
11
|
+
<b>The ultimate guardrail system for AI-assisted coding.</b><br>
|
|
12
|
+
Built for <i>Cursor</i>, <i>Windsurf</i>, and <i>Antigravity</i>.
|
|
13
|
+
</p>
|
|
14
|
+
|
|
15
|
+
[](https://www.npmjs.com/package/tribunal-kit)
|
|
16
|
+
[](LICENSE)
|
|
17
|
+
</div>
|
|
18
|
+
|
|
19
|
+
<br><br>
|
|
20
|
+
|
|
21
|
+
> 🚨 **AI GENERATES CODE. TRIBUNAL ENSURES IT WORKS.**
|
|
22
|
+
> A plug-in `.agent/` intelligence payload that upgrades your IDE with **32 specialist agents**, **25 slash commands**, **8 parallel Tribunal reviewers**, and a core **Swarm/Supervisor** engine.
|
|
23
|
+
|
|
24
|
+
---
|
|
25
|
+
|
|
26
|
+
<br>
|
|
27
|
+
|
|
28
|
+
## ▓▒░ INITIATION SEQUENCE
|
|
29
|
+
|
|
30
|
+
Drop Tribunal into any project. Global or local.
|
|
31
|
+
|
|
32
|
+
```bash
|
|
33
|
+
# Pull the intelligence payload into your project
|
|
34
|
+
npx tribunal-kit init
|
|
35
|
+
```
|
|
36
|
+
*(Installs the `.agent/` architecture directly. No bloat. Pure capability.)*
|
|
37
|
+
|
|
38
|
+
> ⚠️ **CRITICAL PATH WARNING:** Do **not** let your IDE ignore the agents. If using Cursor or Windsurf, keep `.agent/` **out** of `.gitignore` so the IDE can index the commands. Use `.git/info/exclude` instead.
|
|
39
|
+
|
|
40
|
+
<br>
|
|
41
|
+
|
|
42
|
+
## ▓▒░ THE PIPELINE // HOW IT WORKS
|
|
43
|
+
|
|
44
|
+
**Code generation is solved. Code correctness is the frontier.** We enforce a strict **Evidence-Based Closeout**.
|
|
45
|
+
|
|
46
|
+
```diff
|
|
47
|
+
- AI Generates -> Commits to Disk -> You Find Bugs Later
|
|
48
|
+
+ AI Generates -> Parallel Tribunal Review -> Human Gate -> Commits to Disk
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
### 🎯 Auto-Routing Intelligence
|
|
52
|
+
No manual tagging required. The system self-organizes.
|
|
53
|
+
|
|
54
|
+
<p>
|
|
55
|
+
<kbd>User</kbd> "Add JWT authentication" <br>
|
|
56
|
+
<kbd>System</kbd> <code>🤖 Applying @security-auditor + @backend-specialist...</code> <br><br>
|
|
57
|
+
|
|
58
|
+
<kbd>User</kbd> "Fix the dark mode button" <br>
|
|
59
|
+
<kbd>System</kbd> <code>🤖 Applying @ui-ux-pro-max + @frontend-specialist...</code> <br><br>
|
|
60
|
+
|
|
61
|
+
<kbd>User</kbd> "/swarm build a API" <br>
|
|
62
|
+
<kbd>System</kbd> <code>🤖 supervisor-agent → Dispatching 3 Workers...</code>
|
|
63
|
+
</p>
|
|
64
|
+
|
|
65
|
+
<br>
|
|
66
|
+
|
|
67
|
+
## ▓▒░ CAPABILITY MATRIX
|
|
68
|
+
|
|
69
|
+
| System Asset | Count | Operational Scope |
|
|
70
|
+
| :--- | :---: | :--- |
|
|
71
|
+
| 🤖 **Agents** | `32` | Specialist personas (Security, DB Architect, DevOps Responder) |
|
|
72
|
+
| 🧠 **Skills** | `44` | Domain modules (Edge Computing, Red Team Tactics, WebXR) |
|
|
73
|
+
| ⚡ **Workflows** | `25` | Slash command procedures including `/swarm` orchestration |
|
|
74
|
+
| 🛠️ **Scripts** | `13` | CI/CD, linting, payload dispatching, test suite runners |
|
|
75
|
+
|
|
76
|
+
<br>
|
|
77
|
+
|
|
78
|
+
## ▓▒░ COMMAND TERMINAL
|
|
79
|
+
|
|
80
|
+
Expand the accordions to view the operational commands at your disposal.
|
|
81
|
+
|
|
82
|
+
<details open>
|
|
83
|
+
<summary><b>🔥 CORE EXECUTION</b></summary>
|
|
84
|
+
<br>
|
|
85
|
+
|
|
86
|
+
| Command | Action |
|
|
87
|
+
| :--- | :--- |
|
|
88
|
+
| <code>/generate</code> | Trigger full Tribunal: Generate → Audit → Approve. |
|
|
89
|
+
| <code>/create</code> | Scaffold major features or apps, routed by App Builder. |
|
|
90
|
+
| <code>/enhance</code> | Safely extend existing structures without regression. |
|
|
91
|
+
| <code>/deploy</code> | Force the 3-gate production release sequence. |
|
|
92
|
+
|
|
93
|
+
</details>
|
|
94
|
+
|
|
95
|
+
<details>
|
|
96
|
+
<summary><b>⚖️ THE TRIBUNAL GAUNTLET (REVIEWERS)</b></summary>
|
|
97
|
+
<br>
|
|
98
|
+
Unleash parallel reviewers on existing code.
|
|
99
|
+
|
|
100
|
+
| Command | Action |
|
|
101
|
+
| :--- | :--- |
|
|
102
|
+
| <code>/review</code> | Audit code for silent degradation and logic holes. |
|
|
103
|
+
| <code>/tribunal-full</code> | Unleash **ALL 8** reviewers simultaneously. Maximum scrutiny. |
|
|
104
|
+
| <code>/tribunal-backend</code> | Summons <code>[ Logic + Security + Dependency + Types ]</code> |
|
|
105
|
+
| <code>/tribunal-frontend</code> | Summons <code>[ Logic + Security + Frontend + Types ]</code> |
|
|
106
|
+
| <code>/tribunal-database</code> | Summons <code>[ Logic + Security + SQL ]</code> |
|
|
107
|
+
| <code>/tribunal-mobile</code> | Summons <code>[ Logic + Security + Mobile ]</code> |
|
|
108
|
+
|
|
109
|
+
</details>
|
|
110
|
+
|
|
111
|
+
<details>
|
|
112
|
+
<summary><b>🧠 SWARM & ORCHESTRATION</b></summary>
|
|
113
|
+
<br>
|
|
114
|
+
|
|
115
|
+
| Command | Action |
|
|
116
|
+
| :--- | :--- |
|
|
117
|
+
| <code>/swarm</code> | Supervisor breaks goal → sends to isolated workers → synthesizes. |
|
|
118
|
+
| <code>/orchestrate</code> | Manual multi-agent sync for complex integrations. |
|
|
119
|
+
| <code>/plan</code> | Architectural mapping before a single line is written. |
|
|
120
|
+
| <code>/ui-ux-pro-max</code>| Triggers peak aesthetic frontend design. |
|
|
121
|
+
|
|
122
|
+
</details>
|
|
123
|
+
|
|
124
|
+
<details>
|
|
125
|
+
<summary><b>🔧 TROUBLESHOOTING & OPS</b></summary>
|
|
126
|
+
<br>
|
|
127
|
+
|
|
128
|
+
| Command | Action |
|
|
129
|
+
| :--- | :--- |
|
|
130
|
+
| <code>/debug</code> | Systematic root-cause investigation. |
|
|
131
|
+
| <code>/preview</code> | Local development server control. |
|
|
132
|
+
| <code>/status</code> | View Tribunal session status. |
|
|
133
|
+
|
|
134
|
+
</details>
|
|
135
|
+
|
|
136
|
+
<br>
|
|
137
|
+
|
|
138
|
+
## ▓▒░ POST-INSTALL TELEMETRY
|
|
139
|
+
|
|
140
|
+
After initialization, utility scripts unlock local ops:
|
|
141
|
+
|
|
142
|
+
```bash
|
|
143
|
+
# 01. Pre-commit audit
|
|
144
|
+
python .agent/scripts/checklist.py .
|
|
145
|
+
|
|
146
|
+
# 02. Pre-deploy full suite verification
|
|
147
|
+
python .agent/scripts/verify_all.py
|
|
148
|
+
|
|
149
|
+
# 03. Start local development environment
|
|
150
|
+
python .agent/scripts/auto_preview.py start
|
|
151
|
+
```
|
|
152
|
+
|
|
153
|
+
<br>
|
|
154
|
+
|
|
155
|
+
<div align="center">
|
|
156
|
+
<br>
|
|
157
|
+
<img src="https://img.shields.io/badge/Status-Active_&_Secured-00e5ff?style=for-the-badge" alt="Status" />
|
|
158
|
+
<br><br>
|
|
159
|
+
<i>"Never guess database column names. Error handling on every async function. Evidence-based closeouts. Welcome to the Tribunal."</i><br>
|
|
160
|
+
<sub><b>MIT Licensed</b> • Hand-forged for high-performance agentic engineering.</sub>
|
|
161
|
+
</div>
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "tribunal-kit",
|
|
3
|
-
"version": "2.4.
|
|
3
|
+
"version": "2.4.5",
|
|
4
4
|
"description": "Anti-Hallucination AI Agent Kit — 33 specialist agents, 25 slash commands, Swarm/Supervisor engine, and Tribunal review pipeline for Cursor, Windsurf, and Antigravity.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"ai",
|