@rubix0270/arboris 1.0.2 → 1.0.4

package/prisma/skills/team-builder/SKILL.md

@@ -1,169 +0,0 @@
----
-name: team-builder
-description: Interactive agent picker for composing and dispatching parallel teams
-metadata:
-  origin: community
----
-
-# Team Builder
-
-Interactive menu for browsing and composing agent teams on demand. Works with flat or domain-subdirectory agent collections.
-
-## When to Use
-
-- You have multiple agent personas (markdown files) and want to pick which ones to use for a task
-- You want to compose an ad-hoc team from different domains (e.g., Security + SEO + Architecture)
-- You want to browse what agents are available before deciding
-
-## Prerequisites
-
-Agent files must be markdown files containing a persona prompt (identity, rules, workflow, deliverables). The first `# Heading` is used as the agent name and the first paragraph as the description.
-
-Both flat and subdirectory layouts are supported:
-
-**Subdirectory layout** — domain is inferred from the folder name:
-
-```
-agents/
-├── engineering/
-│   ├── security-engineer.md
-│   └── software-architect.md
-├── marketing/
-│   └── seo-specialist.md
-└── sales/
-    └── discovery-coach.md
-```
-
-**Flat layout** — domain inferred from shared filename prefixes. A prefix counts as a domain when 2+ files share it. Files with unique prefixes go to "General". Note: the algorithm splits at the first `-`, so multi-word domains (e.g., `product-management`) should use the subdirectory layout instead:
-
-```
-agents/
-├── engineering-security-engineer.md
-├── engineering-software-architect.md
-├── marketing-seo-specialist.md
-├── marketing-content-strategist.md
-├── sales-discovery-coach.md
-└── sales-outbound-strategist.md
-```
-
-## Configuration
-
-Agents are discovered via two methods, merged and deduplicated by agent name:
-
-1. **`claude agents` command** (primary) — run `claude agents` to get all agents known to the CLI, including user agents, plugin agents (e.g. `everything-claude-code:architect`), and built-in agents. This automatically covers ECC marketplace installs without any path configuration.
-2. **File glob** (fallback, for reading agent content) — agent markdown files are read from:
-   - `./agents/**/*.md` + `./agents/*.md` — project-local agents
-   - `~/.claude/agents/**/*.md` + `~/.claude/agents/*.md` — global user agents
-
-Earlier sources take precedence when names collide: user agents > plugin agents > built-in agents. A custom path can be used instead if the user specifies one.
-
-## How It Works
-
-### Step 1: Discover Available Agents
-
-Run `claude agents` to get the full agent list. Parse each line:
-- **Plugin agents** are prefixed with `plugin-name:` (e.g., `everything-claude-code:security-reviewer`). Use the part after `:` as the agent name and the plugin name as the domain.
-- **User agents** have no prefix. Read the corresponding markdown file from `~/.claude/agents/` or `./agents/` to extract the name and description.
-- **Built-in agents** (e.g., `Explore`, `Plan`) are skipped unless the user explicitly asks to include them.
-
-For user agents loaded from markdown files:
-- **Subdirectory layout:** extract the domain from the parent folder name
-- **Flat layout:** collect all filename prefixes (text before the first `-`). A prefix qualifies as a domain only if it appears in 2 or more filenames (e.g., `engineering-security-engineer.md` and `engineering-software-architect.md` both start with `engineering` → Engineering domain). Files with unique prefixes (e.g., `code-reviewer.md`, `tdd-guide.md`) are grouped under "General"
-- Extract the agent name from the first `# Heading`. If no heading is found, derive the name from the filename (strip `.md`, replace hyphens with spaces, title-case)
-- Extract a one-line summary from the first paragraph after the heading
-
-If no agents are found after running `claude agents` and probing file locations, inform the user: "No agents found. Run `claude agents` to verify your setup." Then stop.
-
-### Step 2: Present Domain Menu
-
-```
-Available agent domains:
-1. Engineering — Software Architect, Security Engineer
-2. Marketing — SEO Specialist
-3. Sales — Discovery Coach, Outbound Strategist
-
-Pick domains or name specific agents (e.g., "1,3" or "security + seo"):
-```
-
-- Skip domains with zero agents (empty directories)
-- Show agent count per domain
-
-### Step 3: Handle Selection
-
-Accept flexible input:
-- Numbers: "1,3" selects all agents from Engineering and Sales
-- Names: "security + seo" fuzzy-matches against discovered agents
-- "all from engineering" selects every agent in that domain
-
-If more than 5 agents are selected, list them alphabetically and ask the user to narrow down: "You selected N agents (max 5). Pick which to keep, or say 'first 5' to use the first five alphabetically."
-
-Confirm selection:
-```
-Selected: Security Engineer + SEO Specialist
-What should they work on? (describe the task):
-```
-
-### Step 4: Spawn Agents in Parallel
-
-1. Read each selected agent's markdown file
-2. Prompt for the task description if not already provided
-3. Spawn all agents in parallel using the Agent tool:
-   - `subagent_type: "general-purpose"`
-   - `prompt: "{agent file content}\n\nTask: {task description}"`
-   - Each agent runs independently — no inter-agent communication needed
-4. If an agent fails (error, timeout, or empty output), note the failure inline (e.g., "Security Engineer: failed — [reason]") and continue with results from agents that succeeded
-
-### Step 5: Synthesize Results
-
-Collect all outputs and present a unified report:
-- Results grouped by agent
-- Synthesis section highlighting:
-  - Agreements across agents
-  - Conflicts or tensions between recommendations
-  - Recommended next steps
-
-If only 1 agent was selected, skip synthesis and present the output directly.
-
-## Rules
-
-- **Dynamic discovery only.** Never hardcode agent lists. New files in the directory auto-appear in the menu.
-- **Max 5 agents per team.** More than 5 produces diminishing returns and excessive token usage. Enforce at selection time.
-- **Parallel dispatch.** All agents run simultaneously — use the Agent tool's parallel invocation pattern.
-- **Parallel Agent calls, not TeamCreate.** This skill uses parallel Agent tool calls for independent work. TeamCreate (a Claude Code tool for multi-agent dialogue) is only needed when agents must debate or respond to each other.
-
-## Examples
-
-```
-User: team builder
-
-Claude:
-Available agent domains:
-1. Engineering (2) — Software Architect, Security Engineer
-2. Marketing (1) — SEO Specialist
-3. Sales (4) — Discovery Coach, Outbound Strategist, Proposal Strategist, Sales Engineer
-4. Support (1) — Executive Summary
-
-Pick domains or name specific agents:
-
-User: security + seo
-
-Claude:
-Selected: Security Engineer + SEO Specialist
-What should they work on?
-
-User: Review my Next.js e-commerce site before launch
-
-[Both agents spawn in parallel, each applying their specialty to the codebase]
-
-Claude:
-## Security Engineer Findings
-- [findings...]
-
-## SEO Specialist Findings
-- [findings...]
-
-## Synthesis
-Both agents agree on: [...]
-Tension: Security recommends CSP that blocks inline styles, SEO needs inline schema markup. Resolution: [...]
-Next steps: [...]
-```

package/prisma/skills/terminal-ops/SKILL.md

@@ -1,110 +0,0 @@
----
-name: terminal-ops
-description: Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.
-metadata:
-  origin: ECC
----
-
-# Terminal Ops
-
-Use this when the user wants real repo execution: run commands, inspect git state, debug CI or builds, make a narrow fix, and report exactly what changed and what was verified.
-
-This skill is intentionally narrower than general coding guidance. It is an operator workflow for evidence-first terminal execution.
-
-## Skill Stack
-
-Pull these ECC-native skills into the workflow when relevant:
-
-- `verification-loop` for exact proving steps after changes
-- `tdd-workflow` when the right fix needs regression coverage
-- `security-review` when secrets, auth, or external inputs are involved
-- `github-ops` when the task depends on CI runs, PR state, or release status
-- `knowledge-ops` when the verified outcome needs to be captured into durable project context
-
-## When to Use
-
-- user says "fix", "debug", "run this", "check the repo", or "push it"
-- the task depends on command output, git state, test results, or a verified local fix
-- the answer must distinguish changed locally, verified locally, committed, and pushed
-
-## Guardrails
-
-- inspect before editing
-- stay read-only if the user asked for audit/review only
-- prefer repo-local scripts and helpers over improvised ad hoc wrappers
-- do not claim fixed until the proving command was rerun
-- do not claim pushed unless the branch actually moved upstream
-
-## Workflow
-
-### 1. Resolve the working surface
-
-Settle:
-
-- exact repo path
-- branch
-- local diff state
-- requested mode:
-  - inspect
-  - fix
-  - verify
-  - push
-
-### 2. Read the failing surface first
-
-Before changing anything:
-
-- inspect the error
-- inspect the file or test
-- inspect git state
-- use any already-supplied logs or context before re-reading blindly
-
-### 3. Keep the fix narrow
-
-Solve one dominant failure at a time:
-
-- use the smallest useful proving command first
-- only escalate to a bigger build/test pass after the local failure is addressed
-- if a command keeps failing with the same signature, stop broad retries and narrow scope
-
-### 4. Report exact execution state
-
-Use exact status words:
-
-- inspected
-- changed locally
-- verified locally
-- committed
-- pushed
-- blocked
-
-## Output Format
-
-```text
-SURFACE
-- repo
-- branch
-- requested mode
-
-EVIDENCE
-- failing command / diff / test
-
-ACTION
-- what changed
-
-STATUS
-- inspected / changed locally / verified locally / committed / pushed / blocked
-```
-
-## Pitfalls
-
-- do not work from stale memory when the live repo state can be read
-- do not widen a narrow fix into repo-wide churn
-- do not use destructive git commands
-- do not ignore unrelated local work
-
-## Verification
-
-- the response names the proving command or test
-- git-related work names the repo path and branch
-- any push claim includes the target branch and exact result

package/prisma/skills/tinystruct-patterns/SKILL.md

@@ -1,279 +0,0 @@
----
-name: tinystruct-patterns
-description: Expert guidance for developing with the tinystruct Java framework. Use when working on the tinystruct codebase or any project built on tinystruct — including creating Application classes, @Action-mapped routes, unit tests, ActionRegistry, HTTP/CLI dual-mode handling, the built-in HTTP server, the event system, JSON with Builder/Builders, database persistence with AbstractData, POJO generation, Server-Sent Events (SSE), file uploads, and outbound HTTP networking.
-metadata:
-  origin: ECC
----
-
-# tinystruct Development Patterns
-
-Architecture and implementation patterns for building modules with the **tinystruct** Java framework – a lightweight, high-performance framework that treats CLI and HTTP as equal citizens, requiring no `main()` method and minimal configuration.
-
-## Core Principle
-
-**CLI and HTTP are equal citizens.** Every method annotated with `@Action` should ideally be runnable from both a terminal and a web browser without modification. This "dual-mode" capability is the core design philosophy of tinystruct.
-
-## When to Activate
-
-### When to Use
-
-- Creating new `Application` modules by extending `AbstractApplication`.
-- Defining routes and command-line actions using `@Action`.
-- Handling per-request state via `Context`.
-- Performing JSON serialization using the native `Builder` and `Builders` components.
-- Working with database persistence via `AbstractData` POJOs.
-- Generating POJOs from database tables using the `generate` command.
-- Implementing Server-Sent Events (SSE) for real-time push.
-- Handling file uploads via multipart data.
-- Making outbound HTTP requests with `URLRequest` and `HTTPHandler`.
-- Configuring database connections or system settings in `application.properties`.
-- Debugging routing conflicts (Actions) or CLI argument parsing.
-
-## How It Works
-
-The tinystruct framework treats any method annotated with `@Action` as a routable endpoint for both terminal and web environments. Applications are created by extending `AbstractApplication`, which provides core lifecycle hooks like `init()` and access to the request `Context`.
-
-Routing is handled by the `ActionRegistry`, which automatically maps path segments to method arguments and injects dependencies. For data-only services, the native `Builder` and `Builders` components should be used for JSON serialization to maintain a zero-dependency footprint. The database layer uses `AbstractData` POJOs paired with XML mapping files for CRUD operations without external ORM libraries.
-
-## Examples
-
-### Basic Application (MyService)
-```java
-public class MyService extends AbstractApplication {
-    @Override
-    public void init() {
-        this.setTemplateRequired(false); // Disable .view lookup for data/API apps
-    }
-
-    @Override public String version() { return "1.0.0"; }
-
-    @Action("greet")
-    public String greet() {
-        return "Hello from tinystruct!";
-    }
-
-    // Path parameter: GET /?q=greet/James  OR  bin/dispatcher greet/James
-    @Action("greet")
-    public String greet(String name) {
-        return "Hello, " + name + "!";
-    }
-}
-```
-
-### HTTP Mode Disambiguation (login)
-```java
-@Action(value = "login", mode = Mode.HTTP_POST)
-public String doLogin(Request<?, ?> request) throws ApplicationException {
-    request.getSession().setAttribute("userId", "42");
-    return "Logged in";
-}
-```
-
-### Native JSON Data Handling (Builder + Builders)
-```java
-import org.tinystruct.data.component.Builder;
-import org.tinystruct.data.component.Builders;
-
-@Action("api/data")
-public String getData() throws ApplicationException {
-    Builders dataList = new Builders();
-    Builder item = new Builder();
-    item.put("id", 1);
-    item.put("name", "James");
-    dataList.add(item);
-
-    Builder response = new Builder();
-    response.put("status", "success");
-    response.put("data", dataList);
-    return response.toString(); // {"status":"success","data":[{"id":1,"name":"James"}]}
-}
-```
-
-### SSE (Server-Sent Events)
-```java
-import org.tinystruct.http.SSEPushManager;
-
-@Action("sse/connect")
-public String connect() {
-    return "{\"type\":\"connect\",\"message\":\"Connected to SSE\"}";
-}
-
-// Push to a specific client
-String sessionId = getContext().getId();
-Builder msg = new Builder();
-msg.put("text", "Hello, user!");
-SSEPushManager.getInstance().push(sessionId, msg);
-
-// Broadcast to all
-// Broadcast to all
-SSEPushManager.getInstance().broadcast(msg);
-```
-
-### File Upload
-```java
-import org.tinystruct.data.FileEntity;
-
-@Action(value = "upload", mode = Mode.HTTP_POST)
-public String upload(Request<?, ?> request) throws ApplicationException {
-    List<FileEntity> files = request.getAttachments();
-    if (files != null) {
-        for (FileEntity file : files) {
-            System.out.println("Uploaded: " + file.getFilename());
-        }
-    }
-    return "Upload OK";
-}
-```
-
-## MCP Server and Tools Integration
-
-tinystruct provides native support for the Model Context Protocol (MCP) starting with SDK version **`1.7.26`**.
-The MCP APIs (e.g., `org.tinystruct.mcp.MCPTool`, `org.tinystruct.mcp.MCPServer`, `org.tinystruct.mcp.MCPException`) are included directly in the core dependency:
-```xml
-<dependency>
-    <groupId>org.tinystruct</groupId>
-    <artifactId>tinystruct</artifactId>
-    <version>1.7.26</version>
-</dependency>
-```
-
-> **SECURITY WARNING (Prompt Injection):**
-> Tool return values are fed directly back into the AI model's context window. You **MUST** validate and sanitize all caller-supplied arguments before including them in the tool's return string. Failure to sanitize inputs can allow an attacker to inject adversarial instructions (Prompt Injection) that override the model's behavior. Always validate length, character sets, and nullity.
-
-**To create an MCP Tool:**
-1. Extend `org.tinystruct.mcp.MCPTool`.
-2. Annotate operations with `@Action` and declare parameters using `@Argument` within the `arguments` array.
-3. Accept parameters as explicit method arguments matching the keys in `@Argument`. (Do **not** use `getContext().getAttribute(...)` for tool arguments).
-
-```java
-import org.tinystruct.mcp.MCPTool;
-import org.tinystruct.mcp.MCPException;
-import org.tinystruct.system.annotation.Action;
-import org.tinystruct.system.annotation.Argument;
-
-public class MyCustomTool extends MCPTool {
-    public MyCustomTool() {
-        super("custom", "A custom tool for demonstrating MCP");
-    }
-
-    @Action(
-        value = "custom/hello",
-        description = "Say hello to someone",
-        arguments = {
-            @Argument(key = "name", description = "The name to greet", type = "string", optional = false)
-        }
-    )
-    public String hello(String name) throws MCPException {
-        // SECURITY: Validate/sanitize tool inputs before returning to the model
-        // to prevent prompt injection vulnerabilities.
-        if (name == null || name.length() > 50 || !name.matches("^[a-zA-Z0-9 ]+$")) {
-            throw new MCPException("Invalid name provided");
-        }
-        return "Hello, " + name + "!";
-    }
-}
-```
-
-**To deploy an MCP Server:**
-1. Extend `org.tinystruct.mcp.MCPServer`.
-2. Override `init()` and register your tools using `this.registerTool()`. The framework automatically scans and maps the `@Action` methods.
-
-```java
-import org.tinystruct.mcp.MCPServer;
-
-public class MyMCPServer extends MCPServer {
-    @Override
-    public void init() {
-        super.init();
-        this.registerTool(new MyCustomTool());
-    }
-
-    @Override
-    public String version() {
-        return "1.0.0";
-    }
-}
-```
-
-Run the server via the dispatcher:
-```bash
-bin/dispatcher start --import org.tinystruct.system.HttpServer --import com.example.MyMCPServer
-```
-
-## Configuration
-
-Settings are managed in `src/main/resources/application.properties`.
-
-```properties
-# Database
-driver=org.h2.Driver
-database.url=jdbc:h2:~/mydb
-database.user=sa
-database.password=
-
-# Server
-default.home.page=hello
-server.port=8080
-
-# Locale
-default.language=en_US
-
-# Session (Redis for clustered environments)
-# default.session.repository=org.tinystruct.http.RedisSessionRepository
-# redis.host=127.0.0.1
-# redis.port=6379
-```
-
-Access config values in your application:
-```java
-String port = this.getConfiguration("server.port");
-```
-
-## Red Flags & Anti-patterns
-
-| Symptom | Correct Pattern |
-|---|---|
-| Importing `com.google.gson` or `com.fasterxml.jackson` | Use `org.tinystruct.data.component.Builder` / `Builders`. |
-| Using `List<Builder>` for JSON arrays | Use `Builders` to avoid generic type erasure issues. |
-| `ApplicationRuntimeException: template not found` | Call `setTemplateRequired(false)` in `init()` for API-only apps. |
-| Annotating `private` methods with `@Action` | Actions must be `public` to be registered by the framework. |
-| Hardcoding `main(String[] args)` in apps | Use `bin/dispatcher` as the entry point for all modules. |
-| Manual `ActionRegistry` registration | Prefer the `@Action` annotation for automatic discovery. |
-| Action not found at runtime | Ensure class is imported via `--import` or listed in `application.properties`. |
-| CLI arg not visible | Pass with `--key value`; access via `getContext().getAttribute("--key")`. |
-| Two methods same path, wrong one fires | Set explicit `mode` (e.g., `HTTP_GET` vs `HTTP_POST`) to disambiguate. |
-
-## Best Practices
-
-1. **Granular Applications**: Break logic into smaller, focused applications rather than one monolithic class.
-2. **Setup in `init()`**: Leverage `init()` for setup (config, DB) rather than the constructor. Do NOT call `setAction()` — use `@Action` annotation.
-3. **Mode Awareness**: Use the `Mode` parameter in `@Action` to restrict sensitive operations to `CLI` only or specific HTTP methods.
-4. **Context over Params**: For optional CLI flags, use `getContext().getAttribute("--flag")` rather than adding parameters to the method signature.
-5. **Asynchronous Events**: For heavy tasks triggered by events, use `CompletableFuture.runAsync()` inside the event handler.
-
-## Technical Reference
-
-Detailed guides are available in the `references/` directory:
-
-- [Architecture & Config](references/architecture.md) — Abstractions, Package Map, Properties
-- [Routing & @Action](references/routing.md) — Annotation details, Modes, Parameters
-- [Data Handling](references/data-handling.md) — Builder, Builders, JSON serialization & parsing
-- [Database Persistence](references/database.md) — AbstractData POJOs, CRUD, mapping XML, POJO generation
-- [System & Usage](references/system-usage.md) — Context, Sessions, SSE, File Uploads, Events, Networking
-- [Testing Patterns](references/testing.md) — JUnit 5 unit and HTTP integration testing
-
-## Reference Source Files (Internal)
-
-- `src/main/java/org/tinystruct/AbstractApplication.java` — Core base class with lifecycle hooks
-- `src/main/java/org/tinystruct/system/annotation/Action.java` — Annotation & Modes
-- `src/main/java/org/tinystruct/application/ActionRegistry.java` — Routing Engine
-- `src/main/java/org/tinystruct/data/component/Builder.java` — JSON object serializer
-- `src/main/java/org/tinystruct/data/component/Builders.java` — JSON array serializer
-- `src/main/java/org/tinystruct/data/component/AbstractData.java` — Base POJO class with CRUD
-- `src/main/java/org/tinystruct/data/Mapping.java` — Mapping XML parser
-- `src/main/java/org/tinystruct/data/tools/MySQLGenerator.java` — POJO generator reference
-- `src/main/java/org/tinystruct/data/component/FieldType.java` — SQL-to-Java type mappings
-- `src/main/java/org/tinystruct/data/component/Condition.java` — Fluent SQL query builder
-- `src/main/java/org/tinystruct/http/SSEPushManager.java` — SSE connection management
-- `src/test/java/org/tinystruct/application/ActionRegistryTest.java` — Registry test examples
-- `src/test/java/org/tinystruct/system/HttpServerHttpModeTest.java` — HTTP integration test patterns

package/prisma/skills/tinystruct-patterns/references/architecture.md

@@ -1,90 +0,0 @@
-# tinystruct Architecture and Configuration
-
-## When to Use
-
-Choose **tinystruct** when you need a lightweight, high-performance Java framework that treats CLI and HTTP as equal citizens. Ideal for microservices, CLI utilities, and data-driven applications with a small footprint and zero-dependency JSON handling.
-
-## How It Works
-
-### Core Architecture
-
-The framework operates on a singleton `ActionRegistry` that maps URL patterns (or command strings) to `Action` objects. When a request arrives, the system resolves the path and invokes the corresponding method handle.
-
-#### Key Abstractions
-
-| Class/Interface | Role |
-|---|---|
-| `AbstractApplication` | Base class for all tinystruct applications. Extend this. |
-| `@Action` annotation | Maps a method to a URI path (web) or command name (CLI). The single routing primitive. |
-| `ActionRegistry` | Singleton that maps URL patterns to `Action` objects via regex. Never instantiate directly. |
-| `Action` | Wraps a `MethodHandle` + regex pattern + priority + `Mode` for dispatch. |
-| `Context` | Per-request state store. Access via `getContext()`. Holds CLI args and HTTP request/response. |
-| `Dispatcher` | CLI entry point (`bin/dispatcher`). Reads `--import` to load applications. |
-| `HttpServer` | Built-in HTTP server. Start with `bin/dispatcher start --import org.tinystruct.system.HttpServer`. |
-
-### Package Map
-
-```
-org.tinystruct/
-├── AbstractApplication.java      ← extend this
-├── Application.java              ← interface
-├── ApplicationException.java     ← checked exception
-├── ApplicationRuntimeException.java ← unchecked exception
-├── application/
-│   ├── Action.java               ← runtime action wrapper
-│   ├── ActionRegistry.java       ← singleton route registry
-│   └── Context.java              ← request context
-├── system/
-│   ├── annotation/Action.java    ← @Action annotation + Mode enum
-│   ├── Dispatcher.java           ← CLI dispatcher
-│   ├── HttpServer.java           ← built-in HTTP server
-│   ├── EventDispatcher.java      ← event bus
-│   └── Settings.java             ← reads application.properties
-├── data/
-│   ├── component/Builder.java    ← JSON object (use instead of Gson/Jackson)
-│   ├── component/Builders.java   ← JSON array
-│   ├── component/AbstractData.java ← base POJO for DB persistence
-│   ├── component/Condition.java  ← fluent SQL query builder
-│   ├── component/FieldType.java  ← SQL-to-Java type mappings
-│   ├── Mapping.java              ← reads .map.xml metadata
-│   ├── DatabaseOperator.java     ← low-level JDBC wrapper
-│   └── FileEntity.java           ← file upload representation
-├── http/                         ← Request, Response, Constants
-│   └── SSEPushManager.java       ← Server-Sent Events management
-└── net/                          ← URLRequest, HTTPHandler (outbound HTTP)
-```
-
-### Template Behavior and Dispatch Flow
-
-By default, the framework assumes a view template is required. If `templateRequired` is `true`, `toString()` looks for a `.view` file in `src/main/resources/themes/<ClassName>.view`. Use `setVariable("name", value)` to pass data to templates, which use `{%name%}` for interpolation.
-
-## Examples
-
-### Minimal Application Initialization
-```java
-@Override
-public void init() {
-    this.setTemplateRequired(false); // Skip .view template lookup for data-only apps
-    // Do NOT call setAction() here — use @Action annotation instead
-}
-```
-
-### Action Definition and CLI Invocation
-```java
-@Action("hello")
-public String hello() {
-    return "Hello, tinystruct!";
-}
-```
-**Execution via Dispatcher:**
-```bash
-bin/dispatcher hello
-bin/dispatcher greet/James
-bin/dispatcher echo --words "Hello" --import com.example.HelloApp
-```
-
-### Configuration Access
-Located at `src/main/resources/application.properties`:
-```java
-String port = this.getConfiguration("server.port");
-```