illuminious-web

Pull Illuminious website code, apply changes, and push to main with build verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tudsds/illuminious.com --skill illuminious-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: illuminious-web
Source: https://github.com/tudsds/illuminious.com/tree/main
Command: npx skills add https://github.com/tudsds/illuminious.com --skill illuminious-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Illuminious website management often requires coordinating code pulls, status checks, checkpoints, content edits, and deployment across multiple files and environments. This skill provides a repeatable, auditable workflow that ensures page modifications, style updates, and new features are implemented consistently and tracked from start to finish.

Core Features & Use Cases

  • Pull latest code and verify project status: reads todo.md, README.md, and SESSION-STATE.md to surface current priorities.
  • Create checkpoints and track progress: records progress in SESSION-STATE.md and updates descriptive checkpoints as tasks are completed.
  • Execute targeted changes and verify outcomes: edits client/src/pages and components, then runs a local build and tests to ensure correctness before pushing to main.
  • Push to main with traceability: commits, pushes, and reports deployment status for auditability.

Quick Start

Command the system to pull the latest code, verify status, create checkpoints, implement requested changes, run tests, and push to main.

Frequently Asked Questions about illuminious-web

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

FAQPage Schema
How do I automate website deployment from git pull to push with build verification?

Automating website deployment involves pulling latest code, applying modifications, running local builds and tests, then pushing to main. This skill provides deterministic execution of the complete workflow with build verification and audit trails.

What is the best way to track website content updates and style tweaks across deployments?

Tracking website updates requires creating checkpoints and recording progress in state files like SESSION-STATE.md. This skill reads todo.md and README.md to surface priorities, then logs task completion for end-to-end auditability across content and style changes.

How do I push code changes to main with build verification and error handling?

Pushing code changes to main with build verification requires editing pages and components, running local builds and tests for correctness, then committing and pushing. This skill guarantees deterministic execution with error handling and deployment status reporting for auditability.

Can I use this workflow for feature additions and content updates on the same website project?

Yes, this workflow operates across content updates, style tweaks, and feature additions within the same project. It edits client source pages and components, verifies outcomes with local builds, and pushes to main with consistent traceability for all modification types.

Does this git workflow require external dependencies to manage pull, checkpoint, and push cycles?

No external dependencies are required to manage the pull, checkpoint, and push cycles. This skill operates independently to read project state files, implement requested changes, run build verification, and push to main with deterministic execution and error handling.

Why does my website deployment workflow lack traceability after pushing changes to main?

Deployment workflows lack traceability when progress is not recorded in state files or checkpoints. This skill reads SESSION-STATE.md and todo.md, updates descriptive checkpoints as tasks complete, and reports deployment status to ensure auditability from pull to push.