Menu
TRIGGER when building a new feature, screen, or endpoint. Gather a context pack with palugada before editing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
TRIGGER when implementing UI from a Figma design, link, or file key — use the figma-bridge MCP (free-plan safe), never the raw API or palugada design for node content.
TRIGGER when the user asks about their Postman collections, saved API requests, endpoints, environments, or wants a curl for an existing request — use the postman-bridge MCP (offline-first).
TRIGGER when fixing a bug, crash, or regression. Gather a context pack with palugada before editing.
TRIGGER for tickets, issues, wiki/Confluence/Notion pages, PRDs, or specs.
TRIGGER for git work — branch, commit, push, rebase/merge conflict, pull/merge request, pipeline. Also when the user mentions gh, glab, GitHub, or GitLab.
TRIGGER when refactoring or restructuring existing code. Gather a context pack with palugada before editing.
| name | palugada-feature |
| description | TRIGGER when building a new feature, screen, or endpoint. Gather a context pack with palugada before editing. |
| allowed-tools | Bash(palugada *), Read, Grep, Glob, Write, Edit |
When you build a feature, get ONE budgeted context pack first:
palugada brief feature <target> # recent changes + symbols + the relevant conventions
Then pull only the rules you need (don't guess — the knowledge lives in the profile):
palugada for <task> # a recipe; `palugada for --list` to see all
palugada q <topic> # a convention; `palugada q --list` to see all
Locate code with the palugada-search skill — never blind-grep.