agentleFS
leonardoaraujosantosleonardoaraujosantos/my_ai_skills/ignite/SKILL.md

ignite

Skill1 starsChanged 4 months agoLicence not identifiedView on GitHub

Cosmos SDK app-chain scaffolding and local development with Ignite CLI. Covers installing a pinned release, which Ignite major matches which Cosmos SDK version, the v30 split (top-level commands now target gno.land, Cosmos tooling moved under `ignite cosmos`), scaffolding chains/modules/messages/queries/list/map/single/type/params and what files each touches, proto/OpenAPI/TS client generation, `chain serve` hot reload, `chain build`/`init`, the `config.yml` reference (accounts, validators, genesis overrides, faucet), and debugging buf/proto, Go toolchain, and depinject/app_config.go wiring failures. Broadcasting to non-local networks and real keys are gated behind explicit approval. Use when the user says "ignite scaffold", "ignite chain serve", "scaffold a cosmos chain/module/message", "add a query/list/map to my module", "regenerate protos", "config.yml for ignite", "faucet", "why won't my ignite chain build", "upgrade ignite", or has a Cosmos SDK project with a config.yml at its root.

  • Pipes a download into a shell

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.