Using Skills

Skills are reusable instruction sets that guide the Locofy CLI agent. Instead of repeating the same prompts every session, you can define standards once and invoke them by name.

When you use skills

During locofy pull or locofy integrate — the CLI uses built-in skills automatically to merge generated code into your project and improve the output. You do not need to manage these.

During Interactive Mode — after locofy convert or locofy pull, you can ask the agent to load a skill and apply it to specific files or screens. This is where skills are most useful for day-to-day work.

Installed skills in your project

When you run locofy init or locofy skills install, Locofy copies editable skills into your project:

locofy skills install

These live at .locofy/locofy/skills/ and cover how the agent enhances code—shared component detection, naming conventions, styling rules, and framework-specific patterns. Open and edit these files to match your team's standards.

Use --framework <name> to override auto-detection, or --force to reinstall (previous versions are backed up automatically).

Custom skills

For conventions that are not covered by the installed skills—migrating CSS Modules to Bootstrap, enforcing a component library, or matching your folder structure—create your own skill. See Creating custom skills.

Custom skills go in the same directory:

Invoking skills in Interactive Mode

Reference a skill by name in your prompt. The agent loads the full instructions and applies them:

Load the css-modules-to-bootstrap skill and convert HeroSection.tsx to use Bootstrap utilities

Apply our enhance-policy rules to clean up naming in the checkout screen

Load the css-modules-to-bootstrap skill for components/Header.tsx only — keep our existing btn-outline-primary variant for secondary actions

Tips

• Name the skill explicitly when you want a specific standard applied.
• Scope to a file or section for faster, more predictable results.
• Edit skills in .locofy/locofy/skills/ when you want permanent changes—the agent reads those files on every session.

Skills vs free-form prompts

Use a skill when you have repeatable standards (styling migrations, component conventions, form patterns). Use a direct prompt for one-off changes ("fix the mobile nav", "rename this prop"). Both work together in the same session.

What's next

• Creating custom skills — define project-specific skills with a SKILL.md file
• Editing code — Interactive Mode prompts and code quality improvements