igniter-js

Implement Igniter.js architecture patterns with type-safe context and telemetry.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nubler-hq/tiny --skill igniter-js
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: igniter-js
Source: https://github.com/nubler-hq/tiny/tree/main/.github/skills/igniter-js
Command: npx skills add https://github.com/nubler-hq/tiny --skill igniter-js

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill consolidates authoritative guidance for mastering the Igniter.js ecosystem, enabling teams to implement its architecture correctly.

Core Features & Use Cases

  • Comprehensive guidance across Core, Store, Agents, Jobs, Mail, Connectors, Storage, Telemetry, and related packages.
  • Enforces a Read-First workflow (via AGENTS.md) to ensure architects and agents consult official docs before implementing patterns.
  • Provides structured patterns for type-safe context injection, error handling, and observability to build deterministic, scalable apps.

Quick Start

Follow the Read-First protocol: identify the Igniter.js package you will work with, locate its AGENTS.md, ingest it, and apply the documented architectural patterns to implement features with proper error handling and telemetry.

Frequently Asked Questions about igniter-js

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

FAQPage Schema
How do I implement type-safe context injection in a scalable application architecture?

Type-safe context injection requires structured patterns for hierarchical context propagation. Using Igniter.js architecture, teams enforce hierarchical context injection to build deterministic, scalable apps with strict type safety across Core, Store, and Agents packages.

What is the Read-First workflow for implementing application architecture patterns?

The Read-First workflow ensures architects consult official documentation before implementing patterns. Teams identify the specific Igniter.js package, locate its AGENTS.md, ingest the authoritative guidance, and apply documented architectural patterns for deterministic implementations.

How do I set up telemetry and observability for distributed jobs and agents?

Telemetry integration for jobs and agents requires structured observability patterns. Igniter.js provides guidance across Jobs, Agents, and Telemetry packages, enforcing feature-specific error classes and observability patterns for deterministic, architecturally sound implementations.

Can I enforce feature-specific error handling across connectors and storage packages?

Yes, feature-specific error classes can be enforced across Connectors and Storage packages. Igniter.js architecture enforces feature-specific error handling and hierarchical context injection, ensuring deterministic implementations across all ecosystem packages including Mail and Core.

What's the best way to document architectural patterns for teams building scalable apps?

Documenting architectural patterns via AGENTS.md and references ensures teams implement architecture correctly. Igniter.js consolidates authoritative guidance across its ecosystem, providing structured patterns for type safety, error handling, and telemetry for deterministic, scalable implementations.

Do I need to follow specific architectural patterns when working with multiple Igniter.js packages?

Yes, following documented architectural patterns is required when working across Igniter.js packages. The ecosystem enforces Read-First workflows, type-safe context injection, feature-specific error classes, and telemetry integration for deterministic, architecturally sound implementations across all packages.