new-feature

Classify and implement new features across bix.bot packages with test-first workflow.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/Xaxis/bix.bot --skill new-feature-xaxis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-feature
Source: https://github.com/Xaxis/bix.bot/tree/main/.claude/skills/new-feature
Command: npx skills add https://github.com/Xaxis/bix.bot --skill new-feature-xaxis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, end-to-end workflow for implementing a new feature in the bix.bot engine or editor, ensuring consistent classification, design, testing, and release practices across packages.

Core Features & Use Cases

  • Structured feature workflow: Step-by-step guidance that maps a feature to core abstractions (Trait, Constraint, Intent, System, Viewport, Schema).
  • Cross-package coordination: Supports engine, editor, and app changes with clear ordering and guardrails.
  • Test-first and release readiness: Emphasizes tests, verification, and updates to public exports and schema types.

Quick Start

Follow the workflow to implement a new feature by classifying it, mapping to core abstractions, writing tests, implementing, verifying, and updating exports.

Frequently Asked Questions about new-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a new feature in the bix.bot engine?

Implementing a new feature in the bix.bot engine requires classifying the change, mapping it to 9 core abstractions like Trait and Intent, writing tests first, and updating public exports and schema types.

What is the structured workflow for adding bix.bot editor improvements?

The structured workflow for bix.bot editor improvements maps changes to core abstractions like Viewport and Schema, enforces a test-first approach, and coordinates updates across the engine and apps.

Can I use this workflow for app-level routing changes in bix.bot?

Yes, this workflow explicitly supports app-level routing changes in bix.bot by providing cross-package coordination that spans the engine, editor, and apps with clear ordering and guardrails.

What are the 9 core abstractions used for bix.bot feature implementation?

The 9 core abstractions for bix.bot feature implementation include Trait, Constraint, Intent, System, Viewport, and Schema, providing a structured mapping for engine and editor changes.

Does bix.bot feature implementation require a test-first approach?

Yes, bix.bot feature implementation requires a test-first approach that emphasizes writing tests, verifying functionality, and updating public exports and schema types before release.

What's the best way to coordinate schema updates across bix.bot packages?

The best way to coordinate schema updates across bix.bot packages is using the structured workflow, which provides clear ordering and guardrails for cross-package changes spanning the engine, editor, and apps.