skills.rest
Sheon-S
Sheon-SCOMMUNITY
Explore all skills by this author →
GitHub

ignition-sdk-core

Analyze Ignition SDK module architecture, scope boundaries, and platform-first design decisions.

Updated Apr 9, 2026
Search Tags:#architecture#sdk#packaging#scope#lifecycle#module#ignition
One-click install
npx skills add https://github.com/Sheon-S/ignition-sdk-agent-kit --skill ignition-sdk-core
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ignition-sdk-core
Source: https://github.com/Sheon-S/ignition-sdk-agent-kit/tree/main/.agents/skills/ignition-sdk-core
Command: npx skills add https://github.com/Sheon-S/ignition-sdk-agent-kit --skill ignition-sdk-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides engineers to design Ignition SDK modules with clear scope boundaries, lifecycle wiring, and packaging considerations, reducing architectural drift across complex repositories.

Core Features & Use Cases

  • Scope rules that categorize code into shared contracts (common), runtime services and gateway APIs (gateway), and designer behavior (designer).
  • Hook rules that keep business logic separate from lifecycle registration and wiring.
  • Deliverables and non-trivial task checklists to ensure verifiable outcomes and smooth handoffs.

Quick Start

Run the Ignition SDK core analysis on the repository using the project scan guidelines to identify existing scopes and task ownership.

Frequently Asked Questions about ignition-sdk-core

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

FAQPage Schema
How do I structure an Ignition SDK module to separate gateway and designer scope boundaries?▼

Structure an Ignition SDK module by categorizing code into shared contracts in common, runtime services in gateway, and designer behavior. This separation enforces clear scope boundaries and reduces architectural drift across complex repositories.

What is the best way to manage hook lifecycle registration in Ignition SDK modules?▼

Manage hook lifecycle registration by keeping business logic strictly separate from lifecycle wiring. Applying this rule ensures platform-first design decisions are maintained and module initialization remains verifiable during handoffs.

How do I package an Ignition SDK module with multiple scopes like client, vision, and embedded web?▼

Package an Ignition SDK module by analyzing platform-first design decisions across common, gateway, designer, client, vision, and embedded web scopes. Enforce repository conventions to ensure correct DTO boundaries and verifiable deliverables.

Does the Ignition SDK core analysis support identifying task ownership and deliverables?▼

Ignition SDK core analysis supports identifying task ownership by applying project scan guidelines to map existing scopes. It generates non-trivial task checklists to ensure verifiable outcomes and smooth handoffs for module deliverables.

Why does my Ignition SDK module architecture drift across different repository scopes?▼

Ignition SDK module architecture drifts when scope boundaries and DTO boundaries are not clearly defined. Applying architectural analysis to separate common, gateway, and designer contracts enforces repository conventions and prevents structural drift.

Related Skills

Explore More Software Engineering Skills→
dtprjdtprj
208

build-and-test

Build and test Java multi-module Maven projects with selective module and test patterns.

Official
Advanced
NintendaDevNintendaDev
16

unikit-architecture

Detect the project tech stack and generate architecture guidelines in ARCHITECTURE.md.

Community
Advanced
Sheon-SSheon-S

ignition-designer-hook

Integrate DesignerHook tasks into Ignition SDK module projects.

Community
Intermediate
GuicedEEGuicedEE
5

guicedee-creator

Scaffold GuicedEE-compliant Maven modules with Maven 4 and JDK 25+ baselines.

Official
Advanced