Skip to content

Instantly share code, notes, and snippets.

@ryansutc

ryansutc/grill-me.md

Last active April 20, 2026 03:59
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save ryansutc/2c59903f81584bfdbfdf8a6b15d6c609 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save ryansutc/2c59903f81584bfdbfdf8a6b15d6c609 to your computer and use it in GitHub Desktop.
Download ZIP
My General Claude Code Skills.md files
Raw
grill-me.md
name grill-me
description Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time.

If a question can be answered by exploring the codebase, explore the codebase instead.

Raw
skills.md
Raw
write-a-prd.md

This skill will be invoked when the user wants to create a PRD. You should go through the steps below. You may skip steps if you don't consider them necessary.

  1. ask the user for a long, detailed description of the problem they want to solve in any potential ideas for solutions.

  2. Explore the repo to verify their assertions and understand the current state of the code base.

  3. Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions 1. by 1.

  4. Once you have a complete understanding of the problems and solution use the template below to write the PRD. The PRD should be written in the plans/prd-name.md file.

Problem Statement

Problem user facing, from user's perspective.

Solution

Solution to problem.

User Stories

A list of numbered user stories. Each should be in format of:

  1. As an I want a so that
1. As a mobile bank customer I want to see balance on my accounts, so that I can make better informed decisions about my spending.

This list of user stories should be extremely extensive and cover all aspects of feature.

Implementation Decisions

a list of implementation decisions that were made. This can include:

  • the modules that will be built modified
  • The interfaces of those modules that will be modified
  • Technical clarifications from the developer
  • Architectural decisions
  • Schema changes
  • API contracts
  • specific interactions

Out of Scope

a description of the things that are out of scope for this PRD.

Further Notes

any other stuff.

Raw
write-a-skill.md

Writing Skills

Process

  1. Gather requirements - ask user about:
  • What task/domain does the skill cover?
  • What specific use case should it handle?
  • Does it need executable scripts or just instructions?
  • Any reference materials to include?
  1. Draft the skill - create:
  • SKILL.md with concise instructions
  • Additional reference files if content exceeds 500 lines
  • Utility scripts if deterministic operations needed
  1. Review with user - present draft and ask:
  • Does this cover your use cases?
  • Anything missing or unclear?
  • Should any section be more/less detailed?

Skill Structure

@ryansutc
Copy link
Copy Markdown
Author

ryansutc commented Apr 19, 2026

name: pnpm-not-found
description: Fix pnpm command not found errors by enabling corepack
disable-model-invocation: true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment