agentleFS
dperezcabreradperezcabrera/pico-skills/.claude/skills/add-app/SKILL.md

add-app

Skill4 starsChanged 4 months agoMITView on GitHub

Scaffold a new pico-boot application. Use when starting a new project or setting up the application skeleton. For multi-module projects, prefer /init-project which uses pico-initializer.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a new application: $ARGUMENTS

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Scaffold Pico Application

Tip: For projects with multiple modules (fastapi, sqlalchemy, celery, etc.), use /init-project instead — it generates the full scaffold with all integrations wired correctly via pico-initializer.

Create a new application: $ARGUMENTS

Project Structure

$ARGUMENTS/
    __init__.py
    main.py
    config.py
    services/
        __init__.py
    repositories/
        __init__.py
    api/
        __init__.py
        controllers.py
    tests/
        __init__.py
        conftest.py
application.yaml
pyproject.toml

main.py

import asyncio
from pico_ioc import configuration, YamlTreeSource, EnvSource
from pico_boot import init

async def main():
    config = configuration(
        YamlTreeSource("application.yaml"),
        EnvSource(),
    )
    container = init(modules=["$ARGUMENTS"], config=config)

if __name__ == "__main__":
    asyncio.run(main())

config.py

from dataclasses import dataclass
from pico_ioc import configured

@configured(prefix="app")
@dataclass
class AppSettings:
    name: str = "$ARGUMENTS"
    debug: bool = False

@configured(prefix="database")
@dataclass
class DatabaseSettings:
    url: str = "sqlite+aiosqlite:///./app.db"
    echo: bool = False
    pool_size: int = 5

application.yaml

app:
  name: $ARGUMENTS
  debug: false

database:
  url: "sqlite+aiosqlite:///./app.db"
  echo: false

fastapi:
  title: "$ARGUMENTS API"
  version: "1.0.0"

pyproject.toml

[project]
name = "$ARGUMENTS"
requires-python = ">=3.11"
dependencies = [
    "pico-ioc>=2.5.2",
    "pico-boot>=0.2.1",
    # "pico-fastapi>=0.4.4",
    # "pico-sqlalchemy>=0.5.3",
    # "pico-celery>=0.2.4",
    # "pico-pydantic>=0.2.4",
]

Checklist

  • Project structure with module separation
  • application.yaml with settings
  • @configured dataclasses for typed settings
  • main.py with pico_boot.init()
  • pyproject.toml with dependencies
  • Tests directory with conftest.py

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.