Results for “readme”

Use when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.

Generates a comprehensive, well-structured README.md file for a project by analyzing the workspace and following best practices.

Publish to npm, create README, set up repo, and log the shipment

Adversarial one-question-at-a-time questioning to verify deep reading comprehension of alignment pages, specs, or any document

Bootstrap Team-Wiki directory with SCHEMA.md, index.md, log.md, and folder READMEs

Biome - Fast all-in-one toolchain for web projects (linter + formatter in Rust, 100x faster than ESLint)

Read a file from an allowed path on the local filesystem

Text Claude from your phone — set up the njerschow/textme daemon so inbound iMessages drive a Claude Code session on your laptop, with voice notes, image input, code execution, and a phone-number whitelist.

Generate and validate repo docs, READMEs, and OSS doc packs. Triggers: "doc", "generate and validate repo docs", "doc skill".

runtime-and-process

Transforms A/B test and product experiment data into actionable readouts with hypothesis, metrics, interpretation, and decision.

Decide where a new tool slots into the chezmoi bootstrap and README. Use when adding a CLI/binary to the host bootstrap so it lands in the right install pass and the right README block. Routes auth-required tools to "Interactive logins" and fire-and-forget binaries to "PATH check".

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting, then commit with git.

Refactors a Python script into a beginner-friendly project with clear comments and a complete markdown tutorial.

Analyze existing code files to generate a project-specific coding standards document, with options for templates, README insertion, and inconsistency detection.

Check whether any custom Claude skills are missing from the skills repo (github.com/Theycallmeholla/skills, cloned at /Users/cursivemedia/skills) and add them in the repo's expected format, update the README index, then commit and push. Use when the user says "sync my skills repo", "check for new skills", "update the skills repo", "push my skills to github", "backup my skills", or right after a new custom skill has been created. Also use for a dry-run check like "are any skills missing from my repo?".

Package and publish a skill to the skills.sh community registry, a public GitHub repo, or both. Load when the user asks to publish a skill, share a skill publicly, submit a skill to the registry, release a skill, or when universal-skill-creator offers publishing as a final step after creation. Also triggers on "push this skill to skills.sh", "make this skill public", "share this skill", or "contribute this skill to the community". Validates quality before publishing, packages correctly (zip for multi-file, .md for atomic), writes a README if missing, and publishes via npx skills CLI.

Approach an app, tool, codebase, website, or product as a genuine first-time user with zero insider context — try it out using only the information provided, get confused where a real newcomer would, and surface the "obvious" questions that people who built or use the thing daily can no longer see. Use this whenever the user wants a first-time-user test, a fresh perspective, a naive walkthrough, a cold read of their README/onboarding/docs/UI, or says things like "pretend you've never seen this", "would a new user get this?", "test my app like a beginner", "what would confuse someone new?", or "give me fresh eyes on this". Also use it when someone wants to find gaps in onboarding, docs, or first-run experience — even if they don't say "fresh eyes" explicitly.