Truc350/WebHomeStay / .agents/skills/basedkit-basedkit-help
basedkit-basedkit-help
VerifiedBasedKit usage guide - just type naturally
basedkit-basedkit-help
Use this skill for the BasedKit command /basedkit-help.
Think harder. All-in-one BasedKit guide. Run the script and present output based on type markers.
Intent Validation
The script uses keyword matching with smart weighting. After getting results, validate against these heuristics:
| Sentence Pattern | Primary Intent | Example |
|---|---|---|
[action verb] my [object] | The action verb | "commit my changes" → git |
[context] [subject noun] | The subject noun | "setup notifications" → notifications |
[noun] [noun] | Last noun (topic) | "discord webhook" → notifications |
Action verbs (high intent when first): fix, test, commit, push, build, create, review, deploy, run, check, find, plan, refactor
Context words (low intent, modify subject): setup, add, start, new, my, the, configure
Override script only if: result clearly mismatches the sentence pattern above. Otherwise trust the algorithm.
Translation
IMPORTANT: Always translate {{args}} to English before passing to script.
The Python script only understands English keywords. If {{args}} is in another language:
- Translate
{{args}}to English - Pass the translated English string to the script
Execution
python .codex/basedkit/scripts/basedkit-help.py "{{args}}"
Output Type Detection
The script outputs a type marker on the first line: @BASEDKIT_OUTPUT_TYPE:<type>
Read this marker and adjust your presentation accordingly:
@BASEDKIT_OUTPUT_TYPE:comprehensive-docs
Full documentation (config, schema, setup guides).
Presentation:
- Show the COMPLETE script output verbatim - every section, every code block
- THEN ADD helpful context:
- Real-world usage examples ("For example, if you're working on multiple projects...")
- Common gotchas and tips ("Watch out for: ...")
- Practical scenarios ("This is useful when...")
- End with a specific follow-up question
Example enhancement after showing full output:
## Additional Tips
**When to use global vs local config:**
- Use global (~/.codex/basedkit/.basedkit.json) for personal preferences like language, issue prefix style
- Use local (./.codex/basedkit/.basedkit.json) for project-specific paths, naming conventions
**Common setup for teams:**
Each team member sets their locale globally, but projects share local config via git.
Need help setting up a specific configuration?
@BASEDKIT_OUTPUT_TYPE:category-guide
Workflow guides for command categories (fix, plan, cook, etc.).
Presentation:
- Show the complete workflow and command list
- ADD practical context:
- When to use this workflow vs alternatives
- Real example: "If you encounter a bug in authentication, start with..."
- Transition tips between commands
- Offer to help with a specific task
@BASEDKIT_OUTPUT_TYPE:command-details
Single command documentation.
Presentation:
- Show full command info from script
- ADD:
- Concrete usage example with realistic input
- When this command shines vs alternatives
- Common flags or variations
- Offer to run the command for them
@BASEDKIT_OUTPUT_TYPE:search-results
Search matches for a keyword.
Presentation:
- Show all matches from script
- HELP user navigate:
- Group by relevance if many results
- Suggest most likely match based on context
- Offer to explain any specific command
- Ask what they're trying to accomplish
@BASEDKIT_OUTPUT_TYPE:task-recommendations
Task-based command suggestions.
Presentation:
- Show recommended commands from script
- EXPLAIN the reasoning:
- Why these commands fit the task
- Suggested order of execution
- What each step accomplishes
- Offer to start with the first recommended command
Key Principle
Script output = foundation. Your additions = value-add.
Never replace or summarize the script output. Always show it fully, then enhance with your knowledge and context.
Important: Correct Workflows
/plan→/code: Plan first, then execute the plan/cook: Standalone - plans internally, no separate/planneeded- NEVER suggest
/plan→/cook(cook has its own planning)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |