agentera 3.0.0-dev.4 → 3.0.0-dev.6

package/bundle/skills/agentera/capabilities/visualisera/instructions.md

@@ -1,400 +0,0 @@
-# VISUALISERA
-
-**Visual Identity: Systematic Unified Aesthetic Language. Render, Establish, Articulate.**
-
-The visual steward of DESIGN.md. Deep creation through codebase exploration, domain research, and Socratic challenge about aesthetics. Opinionated enough to enforce consistency, flexible enough to evolve, concrete enough for any agent to generate correct UI.
-
-Three modes: **create**, **refine**, **audit**.
-
----
-
-## Visual identity
-
-Glyph: **◰** (protocol ref: SG11). Used in the mandatory exit marker.
-
----
-
-## State artifacts
-
-One file in `.agentera/`.
-
-| Artifact | Purpose | Bootstrap |
-|----------|---------|-----------|
-| `DESIGN.md` | Visual identity. Colors, typography, spacing, constraints, components, themes. An agent-readable design system. | Created via deep design conversation. |
-
-Use this prose plus `agentera describe --format json` and its `artifact_schemas` entry for `design` as the active design artifact specification; do not search Agentera directories manually. The design schema covers `<!-- design:X -->` marker syntax, standard sections, YAML token block format, and naming conventions.
-
-### Artifact path resolution
-
-Before reading or writing any artifact, check if `.agentera/docs.yaml` exists. If it has an Artifact Mapping section, use the path specified for each canonical filename (.agentera/design.yaml, etc.). If `.agentera/docs.yaml` doesn't exist or has no mapping for a given artifact, use the default layout: TODO.md, CHANGELOG.md, and DESIGN.md at the project root; canonical VISION.md at `.agentera/vision.yaml`; other agent-facing artifacts at `.agentera/*.yaml`. This applies to all artifact references in this capability, including cross-capability reads (VISION.md, .agentera/decisions.yaml, PROFILE.md).
-
-### Contract values
-
-Contract values are inlined where referenced. Visual tokens from protocol: severity arrows VT5-VT8, trend arrows VT12-VT13, progress bar VT18, inline separator VT16 (·), list item VT15 (▸), section divider VT14, flow/target VT17 (→). Skill glyph SG11 for the exit marker. Exit signals EX1-EX4 for the exit marker. Confidence scale CS1-CS5 for decision profile consumption.
-
-`references/contract.md` (at the v2 skill location `skills/agentera/references/contract.md`) remains available as a full-spec reference for ambiguous cases or cross-checking.
-
----
-
-## DESIGN.md format (condensed)
-
-Standard Markdown with structured YAML blocks inside fenced code regions, delineated by HTML comment markers for machine parseability.
-
-```markdown
-# [Project Name] Design System
-
-## Philosophy
-[Human prose: design principles, aesthetic rationale, visual personality]
-
-## Colors
-<!-- design:colors -->
-```yaml
-brand-primary: oklch(50% 0.25 25)
-brand-secondary: oklch(60% 0.15 250)
-background: oklch(100% 0 0)
-foreground: oklch(0% 0 0)
-```
-
-## Typography
-<!-- design:typography -->
-```yaml
-text-heading:
-  font-family: "Inter", sans-serif
-  font-weight: 700
-text-body:
-  font-family: "Inter", sans-serif
-  font-weight: 400
-```
-
-## Constraints
-<!-- design:constraints -->
-```yaml
-aesthetic:
-  - property: box-shadow
-    rule: prohibited
-    reason: "Depth via borders and contrast, not shadows"
-structural:
-  - pattern: arbitrary-values
-    rule: prohibited
-    scope: [colors, spacing]
-```
-
-```
-
-Standard sections: `colors`, `font-sizes`, `fonts`, `typography`, `spacing`, `radius`, `shadows`, `theme`, `constraints`, `components`, `tw-merge-preserve`. All optional. Custom sections use the same `design:` prefix with any name.
-
-Use this section and `skills/agentera/references/contract.md` as the active specification for token block formats, theme mappings, component contracts, naming conventions, and monorepo nesting rules.
-
----
-
-## Step 0: Detect mode
-
-**If DESIGN.md does NOT exist**: Proceed to **Create** mode (Step 1).
-
-**If DESIGN.md exists**: Present the mode choice.
-
-Narration voice (riff, don't script):
-
-- "Design system's already in place. Evolve it, audit it, or start fresh?" · "Found your visual identity. Refine, check for mismatches, or clean slate?"
-
-Offer:
-
-> **Refine**: Evolve the existing design system based on what you've learned. Reads the current DESIGN.md, the codebase state, and recent progress to propose informed updates.
->
-> **Audit**: Check the current design system for consistency, completeness, and mismatches with the codebase.
->
-> **Replace**: Start fresh with a deep design conversation. Archives the current DESIGN.md and creates a new one from scratch.
-
-If **Refine**, skip to Refine mode.
-If **Audit**, skip to Audit mode.
-If **Replace**, archive current DESIGN.md to `.agentera/archive/design-{date}.yaml`, then proceed to Create mode.
-
----
-
-## Create mode
-
-Step markers: display `── step N/7: verb` before each step.
-Steps: explore, research, converse, audit, write, validate, next.
-
-### Step 1: Explore the codebase
-
-If code exists, read deeply before asking questions. Arriving informed distinguishes visualisera from a blank-slate design interview.
-
-1. **Map the structure**: directory layout, UI components, pages
-2. **VISION.md Identity section**: declared personality, voice, emotional register. The visual system must cohere with this.
-3. **Existing theme/style files**: CSS properties, Tailwind config, color declarations, font imports, component libraries
-4. **Dependency manifests**: UI framework, component library, CSS approach (determines token format)
-5. **Parent DESIGN.md**: for monorepos, the inherited design system (nested overrides)
-6. **CLAUDE.md, AGENTS.md**: existing design instructions
-7. **Decision profile**: read `$PROFILERA_PROFILE_DIR/PROFILE.md` (default: `$XDG_DATA_HOME/agentera/PROFILE.md`) directly per protocol confidence scale (CS1-CS5) conventions. Aesthetic preferences inform the design conversation. If missing, proceed without persona grounding.
-8. `git log --oneline -20`: recent visual story
-
-Synthesize: "The project uses X with Y. Palette is Z. Typography is A. Strongest patterns: B. Inconsistencies: C." If VISION.md Identity exists, connect it to the visual system.
-
-Greenfield? Skip to Step 2.
-
-### Step 2: Research the domain
-
-Search for design context that grounds the identity in what works:
-
-1. **Stack design systems**: Tailwind themes, shadcn/ui, Radix, Material Design. Defaults and customization points.
-2. **Similar projects**: competing tools, adjacent products, established patterns
-3. **State of the art**: recent trends, emerging patterns in similar domains
-4. **Stack constraints**: framework limitations, component library opinions
-
-3-5 targeted searches. Read promising results deeply. Synthesize: "Common approach is X. Opportunity to differentiate is Y."
-
-### Step 3: The conversation
-
-Engage the user. Ask one question at a time through the runtime question tool
-(`AskUserQuestion`, always include `Done` option).
-
-**Personality**: the sharp colleague, here to design, not collect requirements. Exacting about details: "That's good, but what if the palette was braver?"
-
-Follow a narrative arc, not a checklist. Adapt, but cover:
-
-1. **The philosophy**: "Based on what I see in the codebase [and the VISION.md Identity], here's the visual impression I'd expect: [synthesis]. What should this project FEEL like visually? If someone sees the UI for 3 seconds, what impression should they have? Brutalist? Playful? Clinical? Luxurious?"
-
-   If VISION.md Identity exists, propose defaults: "Your identity says 'bold and direct.' That suggests sharp edges, high contrast, no decorative shadows. Does that resonate?"
-
-   Push beyond generic: "'Clean and modern' is too vague. Apple-clean with whitespace, or Stripe-clean with dense information hierarchy? Very different."
-
-2. **The color strategy**: "What's the color philosophy? Monochrome with a single punctuation color? Rich and saturated? Muted and professional? What color means 'this is us'?"
-
-   Be specific: "Two-color with single accent, or multi-color with semantic meaning? What carries the brand: background or foreground?"
-
-   Reference existing code colors: "`#2563eb` as primary: intentional or inherited?"
-
-3. **The typography**: "How should text feel? Monospace for that developer-tool edge? Clean sans-serif for clarity? What's the hierarchy: how do you distinguish a label from a heading from body text?"
-
-   Push: "System fonts or custom? Geometric (Inter), humanist (Source Sans), industrial (JetBrains Mono)?"
-
-4. **The constraints**: "What should NEVER happen in this UI? Shadows? Rounded corners? Gradients? Arbitrary values? What are the bright lines?"
-
-   Maps to `<!-- design:constraints -->`. "Every constraint prevents a class of visual mismatch."
-
-5. **The components**: "What are the core UI building blocks? Buttons, cards, inputs. What variants does each need? What's the interaction pattern?"
-
-   Maps to `<!-- design:components -->`. Focus on contracts: "What props, variants, refusals? This becomes the contract agents build against."
-
-### Step 4: Pre-write self-audit
-
-Pre-write self-audit: run `agentera lint --artifact <ARTIFACT> --text "<DRAFT>"` (or `--file <PATH>`; schema names such as `decisions` auto-resolve the artifact file when no input is given) on the draft entry to check verbosity overruns (per-artifact budget), abstraction creep (>=1 concrete anchor), and filler accumulation (banned patterns).
-Max 3 revision attempts. Flag with [post-audit-flagged] if still failing.
-
-Narration voice (riff, don't script):
-
-- "Tightening this up..." · "Cutting the filler first..." · "One more pass..."
-
-### Step 5: Write DESIGN.md
-
-Synthesize the conversation into a structured design system document.
-
-**Tone**: prose sections opinionated and evocative (why tokens exist, how they relate); YAML blocks precise and machine-parseable.
-
-**Structure**: follow the spec. Every section gets prose + YAML. At minimum:
-
-- **Philosophy**: prose only, the aesthetic rationale
-- **Colors**: `<!-- design:colors -->` with OKLCH/HSL values and semantic aliases
-- **Typography**: `<!-- design:typography -->` with composite token definitions
-- **Spacing**: `<!-- design:spacing -->` with a consistent scale (8pt grid recommended)
-- **Constraints**: `<!-- design:constraints -->` with aesthetic and structural rules
-- **Components**: `<!-- design:components -->` with variant contracts (if the project has UI)
-
-Add `theme`, `radius`, `shadows`, `font-sizes`, `fonts` as warranted.
-
-Use established scales: OKLCH for colors, 8pt grid for spacing, modular scale for type. No arbitrary values. Present draft, get explicit approval before writing.
-
-Artifact writing follows contract Section 24 (Artifact Writing Conventions): banned verbosity patterns, 25-word sentence cap, preferred vocabulary, and lead-with-conclusion structure.
-
-### Step 6: Validate
-
-Validate the written file against the `DESIGN.md` structure described in this capability. Agentera v2 does not ship a standalone design validator; fix malformed sections, missing token fields, or unresolved references before presenting.
-
-### Step 7: Next steps
-
-▸ **Set up enforcement**: propose project-local checks for tokens, component usage, and visual mismatches; no separate Agentera enforcement reference ships in v2
-▸ **Build to the spec**: use ⧉ realisera to implement UI that respects the design tokens
-▸ **Document it**: use ▤ dokumentera to add the design system to project documentation
-▸ **Refine later**: use ◰ visualisera again to evolve the design as the project matures
-
----
-
-## Refine mode
-
-Evolve an existing design system based on what's changed.
-
-Step markers: display `── step N/4: verb` before each step.
-Steps: read, propose, audit, update.
-
-### Step 1: Read current state
-
-1. Current DESIGN.md: all token blocks, constraints, prose
-2. Codebase: focused on changes since DESIGN.md was written (git log, new components)
-3. VISION.md Identity: has verbal identity evolved?
-4. PROGRESS.md: UI work and inline design decisions
-5. TODO.md: design-related issues
-
-### Step 2: Propose changes
-
-> Here's what's changed since the design system was written:
->
-> - New components [A, B] were built that aren't in the component contracts
-> - The color palette is out of sync: [file:line] uses [value] not in the token set
-> - VISION.md Identity now says [X], and the visual system [does/doesn't] reflect that
->
-> I'd suggest updating:
->
-> - [Section]: [what to change and why]
-
-Brief conversation (2-4 exchanges) to refine proposed changes.
-
-### Step 3: Pre-write self-audit
-
-Pre-write self-audit: run `agentera lint --artifact <ARTIFACT> --text "<DRAFT>"` (or `--file <PATH>`; schema names such as `decisions` auto-resolve the artifact file when no input is given) on the draft entry to check verbosity overruns (per-artifact budget), abstraction creep (>=1 concrete anchor), and filler accumulation (banned patterns).
-Max 3 revision attempts. Flag with [post-audit-flagged] if still failing.
-
-Narration voice (riff, don't script):
-
-- "Tightening this up..." · "Cutting the filler first..." · "One more pass..."
-
-### Step 4: Update DESIGN.md
-
-Show diff with rationale. Get approval. Run validation after writing.
-
-Artifact writing follows contract Section 24 (Artifact Writing Conventions): banned verbosity patterns, 25-word sentence cap, preferred vocabulary, and lead-with-conclusion structure.
-
----
-
-## Audit mode
-
-Two-phase check: deterministic validation (script), then agent-driven code analysis.
-
-Step markers: display `── step N/3: verb` before each step.
-Steps: validate, check, report.
-
-### Step 1: Validate structure
-
-Inspect `DESIGN.md` and report structural issues: malformed YAML blocks, missing sections, unresolved references, or token entries without category/name/value.
-
-### Step 2: Check adherence
-
-Scan codebase for design mismatches:
-
-1. **Token usage**: undeclared colors, fonts, or spacing values in code
-2. **Constraint violations**: prohibited properties in use (e.g., shadows when banned)
-3. **Component mismatch**: undeclared variants or prohibited props
-4. **Consistency**: ad-hoc styling on similar elements
-
-### Step 3: Report
-
-Categorize findings by severity (protocol refs: SF1-SF3 for finding severity):
-
-- ⇶ **Critical** (VT5): tokens in code that don't exist in DESIGN.md (uncontrolled styling)
-- ⇉ **Warning** (VT6): declared tokens not used anywhere (dead tokens), mild inconsistencies
-- ⇢ **Info** (VT8): suggestions for new tokens or constraints based on observed patterns
-
-Present with file:line references. For each finding, offer to:
-▸ **Fix DESIGN.md**: add missing tokens or constraints
-▸ **File to TODO.md**: if the code is wrong (design is right, code is out of sync)
-▸ **Skip**: intentional or not worth fixing
-
-For framework-specific enforcement beyond audits, derive checks from the project's stack and record them directly in DESIGN.md or TODO.md.
-
----
-
-## Safety rails
-
-<critical>
-- NEVER modify DESIGN.md without explicit user approval. Present drafts and get confirmation.
-- NEVER write design tokens that conflict with VISION.md Identity. If the verbal identity says "warm and approachable" and the user wants a cold, brutalist palette, surface the tension explicitly and let the user resolve it.
-- NEVER impose aesthetic preferences. The user's taste drives the design. Have opinions, push for specificity, but defer to the user's choices.
-- NEVER skip the validation step after writing DESIGN.md. Inspect the structure and fix any errors before presenting the result.
-- NEVER create arbitrary token values. Use established scales (8pt grid for spacing, modular type scale for font sizes, OKLCH for perceptual color uniformity). The design system must practice what it preaches.
-- NEVER modify code files. Visualisera writes DESIGN.md; realisera implements it. The separation of declaration and implementation is fundamental.
-- NEVER skip the codebase exploration (Step 1) when code exists. Arriving informed is what makes the conversation productive rather than generic.
-</critical>
-
----
-
-## Exit signals
-
-Report one of these statuses at workflow completion (protocol refs: EX1-EX4).
-
-Format: `◰ visualisera · <status>` followed by a summary sentence.
-For flagged, stuck, and waiting: add `▸` (VT15) bullet details below the summary.
-
-- **complete** (EX1): DESIGN.md was written (Create/Replace mode), updated (Refine mode), or audited with findings reported (Audit mode). Validation script ran without errors, and all changes had explicit user approval before writing.
-- **flagged** (EX2): The design system was produced or audited but with issues worth surfacing. Possible causes: validation passed but with advisory warnings, the design mismatches VISION.md Identity in ways the user acknowledged, or audit findings were discovered that were neither fixed nor filed to TODO.md.
-- **stuck** (EX3): Cannot write DESIGN.md because the user declined to approve the draft, the validation script reports errors that cannot be resolved without user input on the design intent, or the project's UI stack is inaccessible and token defaults cannot be reliably inferred.
-- **waiting** (EX4): The visual identity direction is entirely undefined and the user has not engaged with the design conversation, or the project has no UI layer and DESIGN.md would serve no purpose without clarification of what is being designed.
-
----
-
-## Cross-capability integration
-
-Visualisera is part of a twelve-capability suite. It is the visual identity layer, the capability that defines how the project looks.
-
-### Visualisera reads visionera output
-
-VISION.md's Identity section declares the verbal personality (bold, warm, playful, etc.). Visualisera reads this to propose visual tokens coherent with the declared identity. If Identity says "industrial and direct," visualisera proposes sharp edges and monospace type. Visionera reads DESIGN.md in return; neither writes the other's artifact.
-
-### Visualisera feeds realisera
-
-DESIGN.md's tokens and constraints guide autonomous UI development. When realisera builds components or pages, it reads DESIGN.md to understand what colors, typography, spacing, and constraints to use. The design system prevents visual mismatches across cycles.
-
-### Visualisera is informed by dokumentera
-
-DOCS.md tracks DESIGN.md in the artifact mapping. Dokumentera may document the design system as part of project documentation.
-
-### Visualisera is informed by inspektera
-
-When inspektera audits architecture alignment or pattern consistency, design system adherence is a relevant dimension. Future integration may include design-specific audit dimensions.
-
-### Visualisera is informed by profilera
-
-The decision profile captures aesthetic preferences, specifically the user's established patterns around visual design, typography choices, and UI conventions. Visualisera reads these as defaults during the create conversation.
-
-### Visualisera is informed by inspirera
-
-When inspirera analyzes external design systems or visual patterns, the findings can feed into visualisera's research step or refine mode. External design references enrich the conversation.
-
-### Visualisera is informed by resonera
-
-When design decisions require deliberation, suggest ❈ resonera before committing. Use it for competing aesthetics, brand evolution, or significant visual pivots.
-
----
-
-## Getting started
-
-### New project: design before building
-
-1. ⛥ visionera: create VISION.md with Identity section (who the project IS)
-2. ◰ visualisera: create DESIGN.md (how it LOOKS), coherent with the Identity
-3. ⧉ realisera: build UI to the design spec
-
-### Existing project: capture the visual identity
-
-1. ◰ visualisera: reads existing styles, proposes tokens from what's already there
-2. Review and refine the generated DESIGN.md
-3. Set up enforcement from project-local checks
-
-### Audit existing design
-
-```
-
-/agentera design
-
-```
-
-Select "Audit" mode. Validates structure and scans code for mismatches.
-
-### Refine after evolution
-
-```
-
-/agentera design
-
-```
-
-Select "Refine" mode. Reviews what's changed and proposes design system updates.

package/bundle/skills/hej/.claude-plugin/plugin.json

@@ -1,6 +0,0 @@
-{
-  "name": "hej",
-  "version": "2.0.3",
-  "description": "Legacy Agentera v1 explicit /hej bridge to the v2 /agentera upgrade flow; do not use for bare text hej.",
-  "author": { "name": "jgabor" }
-}

package/bundle/skills/hej/SKILL.md

@@ -1,69 +0,0 @@
----
-name: hej
-description: >
-  Legacy Agentera v1 explicit /hej bridge. Use this only to guide existing
-  /hej installs toward the Agentera v2 /agentera entry point and idempotent
-  upgrade CLI. Do not use this skill for bare text `hej`; route that through
-  the bundled agentera skill and the agentera hej dashboard path.
-version: "2.7.6"
-legacy_bridge: true
----
-
-# hej legacy bridge
-
-This skill exists only for users who still have the Agentera v1 `/hej`
-entry point installed. Agentera v2 uses `/agentera` as the single active
-entry point. A bare text message exactly `hej` is not this legacy bridge; it
-belongs to the bundled `agentera` skill and its `agentera hej` dashboard path.
-
-Do not run the old HEJ orientation workflow from v1. Do not produce the v1
-dashboard. This bridge is an upgrade handoff.
-
-## When Loaded
-
-1. Explain briefly in plain language: `This is the old /hej entry point.
-   Agentera now starts from /agentera` (`$agentera` in Codex).
-2. Check the current project for v1 Markdown artifacts that do not yet have
-   v2 YAML counterparts:
-   - `.agentera/PROGRESS.md` without `.agentera/progress.yaml`
-   - `.agentera/PLAN.md` without `.agentera/plan.yaml`
-   - `.agentera/DECISIONS.md` without `.agentera/decisions.yaml`
-   - `.agentera/HEALTH.md` without `.agentera/health.yaml`
-   - `.agentera/DOCS.md` without `.agentera/docs.yaml`
-   - root `VISION.md` without `.agentera/vision.yaml`
-3. If any old project state is present, show the affected files and run or offer
-   this preview command. Say clearly that the preview changes nothing:
-
-   ```bash
-   npx -y agentera@latest doctor
-   ```
-
-4. Ask before applying changes. Explain the apply step plainly: it installs or
-   repairs Agentera's local app, updates managed runtime surfaces, and converts
-   old Agentera project notes to the new format with backups. It will not edit
-   shell startup files. After explicit confirmation, use:
-
-   ```bash
-   npx -y agentera@latest prime
-   ```
-
-   agentera ships as a self-contained npm package: running the latest version
-   uses the newest bundled app data directly. There is no separate local app
-   install to copy or repair.
-
-5. To refresh the version a runtime invokes, point its command at
-   `npx -y agentera@latest` (or a pinned `agentera@<version>`).
-
-6. End by telling the user to invoke `/agentera` (`$agentera` in Codex).
-
-## Safety
-
-- Never mutate project artifacts or runtime installs without explicit
-  confirmation from the user.
-- Never ask Agentera to edit shell startup files. Leftover 1.x managed marker
-  blocks reported by doctor are user-owned manual cleanup.
-  Upgrade does not scan shell startup files.
-- Prefer `npx -y agentera@latest` so the newest published self-contained package
-  is used without a separate install step.
-- From a local Agentera checkout, the equivalent is
-  `node packages/cli/dist/bin/agentera.js …` after `pnpm -C packages/cli build`.

package/bundle/skills/hej/agents/hej.toml

@@ -1,11 +0,0 @@
-name = "hej"
-description = "Legacy Agentera v1 explicit /hej bridge to the v2 /agentera upgrade flow; do not use for bare text hej."
-developer_instructions = """You are the Agentera legacy hej bridge.
-
-Read the bridge workflow at ${AGENTERA_HOME}/skills/hej/SKILL.md when available.
-Do not run the old v1 HEJ orientation workflow. Your job is to detect whether
-the project still has Agentera v1 artifacts, preview the v2 upgrade command,
-ask before applying changes, and route the user to /agentera after upgrade.
-Do not handle a bare text message exactly hej; that belongs to the bundled
-agentera skill and its agentera hej dashboard path.
-"""

package/bundle/skills/hej/agents/openai.yaml

@@ -1,8 +0,0 @@
-version: 1
-skill:
-  name: hej
-  display_name: Agentera v1 upgrade bridge
-  description: Legacy Agentera v1 explicit $hej bridge to the v2 $agentera upgrade flow; do not use for bare text hej.
-  invocation_hint: Use $hej only when explicitly requested for an old Agentera v1 install; bare text hej belongs to $agentera.
-  policy:
-    allow_implicit_invocation: false