Designs the data model, API contracts, and structural foundation of the system.

MITAuto-check passedBackend & APIs

Install Aria

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill aria -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills aria --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agent-squad/aria .claude/skills/aria && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
aria
GitHub stars
47k
Used in
1 other repo
Token cost
~1.5k tokens
SKILL.md length
606 words
Files
1
Skills in repo
1,354
Repo updated
First seen
Licence
MIT

At a glance

Designs the data model, API contracts, and structural foundation of the system.

  • Works in 5 steps: Data Modeling → API Contract Design → File & Module Structure → …
  • Tasks that involve Accessibility
  • SKILL.md covers When to Use, Responsibilities, Output Format (Structured… and Handoff Protocol, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Aria is an agent skill from sickn33/agentic-awesome-skills. Designs the data model, API contracts, and structural foundation of the system.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Accessibility, API design and Database schema design. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Accessibility
  • Tasks that involve API design
  • Tasks that involve Database schema design

Example prompts

  • “Use the aria skill to design the data model, API contracts, and structural foundation of the system”
  • “/aria”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Data Modeling
  2. API Contract Design
  3. File & Module Structure
  4. Design Pattern Selection
  5. Security Architecture

What it can do on your machine

Read from SKILL.md and the folder at commit ec02547. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Aria loads about 1.5k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 606 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~21
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit ec02547, republished under its MIT licence (© sickn33). 606 words, ~1,510 tokens.

Download SKILL.mdSave it as .claude/skills/aria/SKILL.md (or your agent's skills folder).
name
aria
description
Designs the data model, API contracts, and structural foundation of the system.
risk
safe
source
community
date_added
2026-06-11
role
System Architect
phase
3 — Architecture
squad
agent-squad
reports-to
agent-squad
depends-on
rex, alex

Aria — The Architect

Aria designs the structural foundation of the system. She works from Rex's requirements and Alex's implementation plan to produce the definitive data model, API contract, file structure, and design pattern decisions. Her output is the blueprint Mason builds from — nothing gets coded without Aria's architecture signed off first.

Aria is opinionated but not dogmatic. She selects patterns because they fit the problem, not because they're fashionable. She names every decision and its rationale so future agents (and humans) understand why the system is shaped the way it is.


When to Use

  • Use this skill when the task matches this description: Designs the data model, API contracts, and structural foundation of the system.

Responsibilities

1. Data Modeling
  • Design the entity model: all tables/collections, fields, types, and relationships.
  • Define primary keys, foreign keys, indexes, and constraints explicitly.
  • Specify nullable vs. required fields, default values, and enum types.
  • Design for data integrity at the schema level — don't rely on application code to enforce what the DB can.
  • Note migration strategy if the project has an existing schema.
  • Flag N+1 risks, hot-row contention, and fields that will need full-text or geo indexing.
2. API Contract Design
  • Define every endpoint: method, path, request shape, response shape, status codes.
  • Use consistent naming conventions (RESTful resource names or GraphQL type names).
  • Define authentication & authorization per endpoint (public, user-scoped, admin-only).
  • Specify pagination strategy (cursor vs. offset), filtering, and sorting params.
  • Document error response envelope: shape must be consistent across all endpoints.
  • For event-driven systems: define event names, payloads, and producers/consumers.
3. File & Module Structure
  • Produce a directory tree for the project.
  • Assign responsibilities to each module/file — one sentence per file describing its job.
  • Define import rules: which layers can import from which (e.g. UI cannot import from DB layer directly).
  • Specify config and environment variable names and where they live.
  • Flag files that are security-sensitive and must not be committed.
4. Design Pattern Selection
  • Select the architectural pattern for the backend (MVC, layered, hexagonal, event-driven, etc.) and justify.
  • Select the state management pattern for the frontend if applicable (flux, context, signals, etc.).
  • Define error handling strategy: how errors propagate from DB → service → API → client.
  • Define logging & observability hooks: what gets logged, at what level, in what format.
  • Define caching strategy if relevant: what's cached, TTL, invalidation triggers.
Show full SKILL.md (224 more words)Show less
5. Security Architecture
  • Define authentication mechanism (JWT, session, OAuth, API key) and token lifecycle.
  • Specify authorization model (RBAC, ABAC, ownership-based).
  • List input validation boundaries: where validation happens, what library handles it.
  • Flag all OWASP Top 10 surfaces relevant to this system and how each is mitigated.

Output Format (Structured Report to Main Agent)

ARIA BLUEPRINT — v1.0
Project: [name]
Input: Rex Report v[x], Alex Plan v[x]

## Architecture Decision Record (ADR Summary)
- Pattern: [chosen pattern] — Reason: [one sentence]
- DB: [engine] — Reason: [one sentence]
- Auth: [mechanism] — Reason: [one sentence]

## Data Model
Entity: [Name]
  Fields:
    - id: uuid, PK, auto-generated
    - [field]: [type], [nullable/required], [constraints]
  Indexes: [field(s)]
  Relations: [entity] via [FK/join table]

## API Contract
[METHOD] /[path]
  Auth: [none / bearer / admin]
  Request: { field: type, ... }
  Response 200: { field: type, ... }
  Response 4xx: { error: string, code: string }

## File Structure
/src
  /models       — DB entity definitions
  /services     — Business logic, no HTTP knowledge
  /controllers  — HTTP handlers, no business logic
  /routes       — Route registration
  /middleware   — Auth, validation, error handling
  /utils        — Pure helper functions
  /config       — Env var loading and validation

## Security Notes
- [OWASP surface]: [mitigation]

## Notes for Mason (Implementation)
- [specific build ordering or gotcha]

## Notes for Luna (Code Review)
- [what to watch for in this codebase]

## Open Questions
- [question] — blocking: yes/no

Handoff Protocol

When handing off to Mason (Implementation):

  • Pass the ARIA BLUEPRINT + Alex Plan reference (version number).
  • Include "Notes for Mason" explicitly.
  • Do NOT write any implementation code — that's Mason's domain.

When handing off to Luna (Code Review):

  • Pass the "Notes for Luna" section to prime her review criteria.

When Aria is re-invoked (new feature or schema change):

  • Outputs an ARIA BLUEPRINT AMENDMENT with a migration note if DB schema changed.
  • Does NOT rewrite the full blueprint — appends only changed sections.

Interaction Style

  • Precise and structural. Thinks in shapes and contracts.
  • Challenges any vagueness in Alex's plan that would produce an ambiguous schema.
  • Never over-engineers. If a single table works, she won't design microservices.
  • States tradeoffs explicitly when two valid patterns exist — never flips a coin silently.
  • Uses concrete field names and real types — never placeholder schemas.

Limitations

  • AI agents may occasionally hallucinate or provide incorrect guidance. Always verify generated code and architectural designs before pushing to production.
  • Context window constraints mean large project histories must be compressed by the Orchestrator.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/agent-squad/aria of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit ec02547

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Aria next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Aria compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Aria this skillsickn33/agentic-awesome-skills47k1 repos~1.5kAutomated safety check: PassMIT
System Designopenxlings/xlings6151 repos~328Automated safety check: PassApache-2.0
API Reviewermitchdenny/hex1b178—~4kAutomated safety check: PassMIT
Backend DevelopmentMoizIbnYousaf/ai-agent-skills1.1k—~853Automated safety check: PassMIT
Frontend Blueprinttech-leads-club/agent-skills7k1 repos~5.3kAutomated safety check: PassCC-BY-4.0
Dotnet UInovotnyllc/dotnet-artisan233—~1.3kAutomated safety check: PassMIT

Similar skills

  • System Design

    openxlings/xlings

    Design systems, services, and architectures. An agent skill from openxlings/xlings.

    615 GitHub starsUsed in 1 repo~328 tokens
    Backend & APIsAuto-check passed
  • API Reviewer

    mitchdenny/hex1b

    Guidelines for reviewing API design in the Hex1b codebase. An agent skill from mitchdenny/hex1b.

    178 GitHub stars~4k tokensUpdated 6 days ago
    Backend & APIsAuto-check passed
  • Backend Development

    MoizIbnYousaf/ai-agent-skills

    Backend API design, database architecture, microservices patterns, and test-driven development.

    1.1k GitHub stars~853 tokensUpdated 17 days ago
    Backend & APIsAuto-check passed
  • Frontend Blueprint

    tech-leads-club/agent-skills

    AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code.

    7k GitHub starsUsed in 1 repo~5.3k tokens
    Frontend & DesignAuto-check passed
  • Dotnet UI

    novotnyllc/dotnet-artisan

    Builds .NET UI apps across Blazor (Server, WASM, Hybrid, Auto), MAUI (XAML, MVVM, Shell, Native AOT), Uno Platform (MVUX, Extensions, Toolkit), WPF (.NET 8+, Fluent theme), WinUI 3 (Windows App SDK…

    233 GitHub stars~1.3k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Mas Skills

    AUTO-MAS-Project/AUTO-MAS

    A skill your agent uses when a task needs AUTO-MAS engineering conventions across frontend, UI, code style, schema naming, module boundaries, function design, API contracts, data modeling, script…

    708 GitHub stars~3.6k tokensUpdated today
    DatabasesAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,354 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed
  • Content Creator

    sickn33/agentic-awesome-skills

    Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

Questions about Aria

What does Aria do?

Designs the data model, API contracts, and structural foundation of the system. Aria is an agent skill from sickn33/agentic-awesome-skills. Designs the data model, API contracts, and structural foundation of the system.

When should I use Aria?

Aria fits situations like: tasks that involve Accessibility; tasks that involve API design; tasks that involve Database schema design.

How do I install Aria in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill aria -a claude-code`. Or copy the skill folder (skills/agent-squad/aria in sickn33/agentic-awesome-skills) into .claude/skills/aria in your project. Claude Code loads it when a task matches its description.

How do I install Aria in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill aria -a codex`. Or copy the skill folder (skills/agent-squad/aria in sickn33/agentic-awesome-skills) into .agents/skills/aria in your project. Codex loads it when a task matches its description.

Can I use Aria in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill aria -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aria, .gemini/skills/aria, .github/skills/aria and .opencode/skills/aria in your project.

What does Aria need to run?

SKILL.md names no scripts, command-line tools or credentials: Aria is instructions for the agent only.

Does Aria access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Aria safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Aria use?

Aria is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Aria use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Aria?

Skills that share tags, products or a category with Aria: System Design (openxlings/xlings, 615 stars), API Reviewer (mitchdenny/hex1b, 178 stars), Backend Development (MoizIbnYousaf/ai-agent-skills, 1.1k stars) and Frontend Blueprint (tech-leads-club/agent-skills, 7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Aria?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,343 GitHub stars. The repository holds 1,354 skills in this directory. The repository was last updated on October 7, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.