One-click install
npx skills add https://github.com/puwenjunluck-pixel/aioncode --skill save-puwenjunluck-pixel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save
Source: https://github.com/puwenjunluck-pixel/aioncode/tree/main/skills/save
Command: npx skills add https://github.com/puwenjunluck-pixel/aioncode --skill save-puwenjunluck-pixel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The save Skill addresses the challenge of maintaining a structured knowledge base for a project by automating the saving of session artifacts into the .aion/ directory.

Core Features & Use Cases

  • Session Artifact Saving: Captures decisions, specifications, plans, and rules during project discussions.
  • Version Control Integration: Ensures all saved artifacts are versioned and can be audited.
  • User Confirmation: Before saving, users confirm the content to ensure accuracy.

Quick Start

Save the current session to the project's .aion/ directory using the /aion:save command.

Frequently Asked Questions about save

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

FAQPage Schema
How do I save session artifacts for version control and project knowledge?

To save session artifacts for version control, you can automate the capture of decisions and specifications into a structured `.aion/` directory, ensuring they are versioned and ready for audit.

What is the best way to maintain a structured knowledge base from project discussions?

Maintaining a structured knowledge base from project discussions is achieved by capturing decisions, plans, and rules as session artifacts and saving them automatically into a dedicated `.aion/` directory.

Do I need to manually validate content before saving session artifacts?

Yes, you need to validate content manually before saving session artifacts, because the process requires user interaction to confirm the captured artifacts and ensure accuracy prior to writing them to the directory.

How does saving session artifacts into a .aion directory work for code repository audits?

Saving session artifacts into a `.aion` directory for code repository audits works by capturing project specifications and rules, then writing them as versioned files to ensure historical traceability.

Can I use this automated artifact saving without an existing code repository?

Automated artifact saving creates a structured `.aion/` directory for version control, but without an existing code repository, you cannot fully utilize the built-in versioning and audit capabilities for your project knowledge.