What problem does it solve? Code changes in a large multi-platform ecosystem risk breaking architecture, losing user work, or skipping validation. This Skill provides a disciplined engineering lane for implementing, refactoring, debugging, and testing code inside the SEIS repository while preserving uncommitted work, main-branch safety, security, and documentation quality. ## Core Features & Use Cases - Architecture-aware implementation: Maps each change to the correct lane (Apple platforms, web, backend/API, MCP/plugin, automation, CI) before editing, using existing scripts and typed APIs instead of ad hoc patterns. - Safety-first workflow: Inspects git status, branch, and remotes first, makes the smallest durable change, and never discards uncommitted work or exposes secrets. - Validation and quality gates: Runs repo-provided checks such as npm run seis:check and package-local tests, scaling validation only when risk requires it. - Use Case: Ask the agent to fix a bug in a SEIS web surface; it reads nearby docs and manifests, makes a minimal typed change, runs the repo's check scripts, and records durable decisions in documentation. ## Quick Start Use $seis-code to implement a scoped SEIS code change safely, for example fixing a bug in the web app and validating it with the repo's check scripts.