AgentToolHub
SkillClaude CodeCursorClineOpenClawWindsurfVS CodeChatGPT

frontend-experience-extractor

Aircury AI Framework

Features

  • ✓Meta-framework for AI-assisted software engineering
  • ✓Integrates OpenSpec, Spec Kit, and Airsync
  • ✓Adaptive workflow routing based on task complexity
  • ✓Enhances code quality and consistency
  • ✓Supports diverse task scopes from routine to complex

Installation Guide

Run the installer from any project directory (or your home directory for a global setup):

bash
bunx @aircury/ai-framework
# or
npx @aircury/ai-framework

The interactive TUI will ask:

  • Scope — Local to configure the current project, Global to configure your machine.

  • AI tools — select the tool-specific integrations you want.

  • Standards modules — for local installs, choose which optional standards this project should enforce.

  • Skill groups — choose which grouped workflows to install through npx skills add.

    • The installer writes all required configuration files, starter spec folders, and agent instructions to the right locations for each tool. Skills are installed through the standard npx skills add ... flow so they remain tracked by the skills ecosystem and can be updated later with npx skills update. Skill installation is driven by a static catalog in src/skills-catalog.ts, so Aircury and curated external skills can be selected through the same interactive flow. If files already exist you can choose to skip them or overwrite them.

    What gets installed

    | Scope | Installed outputs |
    |-------|-------------------|
    | Local | FRAMEWORK.md, AGENTS.md, .aircury/framework.config.json, specs/features/README.md, optional specs/decisions/README.md, plus selected tool-specific files; skills installed via npx skills |
    | Global | Skills installed via npx skills for the selected agents |

    Standards modules

    Local installs persist the selected modules in .aircury/framework.config.json.
    Each module is a small content package with machine-readable metadata plus document fragments, and the final FRAMEWORK.md / AGENTS.md files are rendered from dedicated templates.

    Current built-in modules:

  • decision-records

  • testing

  • hexagonal-architecture

  • ddd

  • token-efficiency

    • The installer and template generation are registry-driven, so adding a new standards module only requires:

  • adding its manifest and content fragments under standards/modules/<module-id>/

  • wiring it into the registry

  • letting the renderer compose it through the shared templates

    • ---

    Reviews