dbtinoy-dbtinoy-/lexigram-framework-skills/cli-project-scaffolding/SKILL.md

cli-project-scaffolding

Skill1 starsChanged 3 months agoMITView on GitHub

Use when creating a new Lexigram project, scaffolding an extension package, or setting up configuration in an existing project

In this repository17 other files it gives its agents.
- ai-subsystem-quickstartSkill
- auth-and-securitySkill
- caching-patternsSkill
- cli-code-generationSkill
- cli-config-and-inspectSkill
- cli-database-operationsSkill
- configuration-managementSkill
- creating-providers-and-modulesSkill
- database-repository-patternSkill
- events-and-messagingSkill
- lexigram-uiSkill
- multimedia-generationSkill
- real-time-webSkill
- resilience-patternsSkill
- testing-with-lexigramSkill
- using-result-and-error-codesSkill
- web-controllers-and-routingSkill

The file

Create a free account to mount

Files

SKILL.md

CLI Project Scaffolding

Overview

The lexigram new and lexigram init commands create project skeletons. lexigram add installs and configures extension packages.

Creating a Project

lexigram new project my-app                     # web-api template (default)
lexigram new project my-app --template api      # JSON API only
lexigram new project my-app --template full     # web + db + auth + cache
lexigram new project my-app --interactive       # prompts: template, DB (sqlite/postgres/none), auth (none/jwt)

Flags: --template/-t, --directory/-d, --interactive/-i.

Scaffolding an Extension

lexigram new package my-feature              # → lexigram-my-feature/

Generates: src/lexigram/my_feature/__init__.py + di/provider.py, plus pyproject.toml, README.md, and a tests/unit/test_provider.py.

Adopting Lexigram in Existing Projects

lexigram init                                # minimal application.yaml
lexigram init --full                         # all sections (web, db, auth, cache...)
lexigram init --force                        # overwrite existing config

Adding Packages

lexigram add database                        # installs package + database: config block
lexigram add auth                            # installs package + auth: config block

Available providers: database, auth, ai, cache, queue, messaging, notification, events, search, storage, monitor, tasks, graphql. Skips sections that already exist in application.yaml.

The add command edits pyproject.toml and patches application.yaml with the provider's default configuration.

Quick Reference

Command	Use Case
`new project <name>`	Full app from template
`new package <name>`	Reusable extension
`init`	Config into existing dir
`add <package>`	Install + configure

Common Mistakes

Running new project inside an existing project — use a fresh directory
Forgetting --interactive — default template has no DB or auth
Running init after new project redundant — new already generates config

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.

Check your setup, free