Vibe coding setup

Each skill guides a specialty. Shared working rules cover planning, research and review; the tools below support parts of that work and require their own installation. Choose what fits your environment in Claude Code or Codex. The guide separates environment configuration from your first project and explains what to check before starting. To try it, start with Claude Code or Codex and one skill. Add components as the work requires.

What is a skill?

A skill is a set of instructions an assistant consults for a type of work. SKILL.md introduces the workflow; supporting guides go deeper into its decisions. You can read, adapt and use the files in your own environment. The result also depends on the context you provide and how the work is reviewed.

Choose your Free skill

Six separate Free downloads, with instructions in English, README and license. Tools and their licenses are separate from the Noha files.

Want the full process?

Pro expands each specialty’s scope. The suite contains all six Pro skills, including portable Edit, plus working premises and manual setup.

Choose your Pro skill

Purchases are temporarily unavailable. Free downloads remain available.

Explore the suite and prices ↗

Download a Free edition and read its scope.

Choose Coding, Design, Mobile, Motion, Copy or Edit. Extract the ZIP and read README.md, SKILL.md and LICENSE. Free resolves a bounded task; full-method materials belong to Pro.

Install the folder ending in -free.

For Claude Code, copy the selected folder to ~/.claude/skills; for Codex, to ~/.agents/skills. For example: ~/.agents/skills/noha-design-free. Back up before replacing any version. Keep the -free folder, reopen the session and explicitly request the installed edition. These paths require an environment that recognizes personal skills.

Check tools and local instructions.

Installation is manual and does not install dependencies. Preserve project rules and confirm the editor, tests, sources, permissions and tools your task requires. The Pro suite includes working premises and manual setup guidance. Subscriptions, APIs, editors and renderers are separate.

Start with a bounded task.

Explain what you want to create or improve, provide the project and available references, and request the relevant skill. An existing web interface can start with Design; a native app with Mobile; software implementation with Coding.

Check the delivery.

Ask for files, decisions and completed checks. Installation, skill use and verified results are different states. Unavailable tools or tests should be recorded as outstanding.

Why we use each component

Superpowers

Helps clarify what to build before implementation and organizes planning, execution and review.

Ponytail

Guides code changes from the existing project, preserving validation and avoiding unnecessary complexity.

Caveman

Keeps the conversation concise. Explanations and deliverables stay complete when the work requires it.

Context7

Consults documentation for the project’s libraries, grounding implementation decisions in the relevant version.

Graphify

Helps investigate file relationships and the impact of changes. Findings must be confirmed in the code.

Claude-Mem

Keeps decisions and discoveries so you can resume in another session without re-explaining the work or resending the entire history. Selective retrieval and shorter sessions can reduce tokens spent reconstructing context. Recording, summarizing and retrieving memory also uses tokens; savings are neither automatic nor guaranteed. Verify capture and retrieval in your environment.

Check your first session

Ask the assistant to locate the skill and explain its scope before executing.
If you configured a hook, look for evidence it delivered context. Recalling a rule does not prove a hook ran.
Confirm available tools, permissions and checks. A missing configuration must not be represented as working.