Repository intelligenceRepositories
⌘K
Home / Repositories / langgptai/awesome-claude-prompts / Instruction Manual
Instruction Manual · Apple silicon · macOS Tahoe

langgptai/awesome-claude-prompts Instruction Manual

Community collection of Claude prompt examples across coding, writing, marketing, business, analysis, and education.

Beginner-friendlyCopy-paste examplesFirst-party sources checked
GitHubRepository profileInstallation Guide

What langgptai/awesome-claude-prompts is—in plain language

Community collection of Claude prompt examples across coding, writing, marketing, business, analysis, and education.

Mental model: This is a catalog. Its job is to help you discover other projects; selecting an entry does not install it. Open the linked project's own documentation before running anything.
Interfacesconfiguration-only
Primary languageMarkdown
Typical useBrowse/copy/adapt prompt patterns for inspiration; treat as examples rather than a runtime.

Your first 15 minutes

  1. Complete the linked Installation Guide and its verification step.
  2. Create a disposable test folder or use non-sensitive sample data.
  3. Run the small example below and observe what files, ports, or prompts appear.
  4. Read the result before approving writes, network calls, account access, or costs.
  5. Only then repeat the workflow with a real project.
Starter workflow
I am reading code for a python game. Explain to me how it works.
Open Installation GuideOpen upstream README

Complete indexed functionality map

Each card below corresponds to a component identified in the repository research. Open a component record for its path, purpose, capabilities, dependencies, risks, and relationships.

Upstream feature-by-feature guide

These capabilities are derived from the current first-party README and supporting documentation. Names follow upstream terminology so you can search the source documentation precisely.

Upstream capability

Claude official prompt resource:

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns claude official prompt resource:. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Contents

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns contents. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

AI Resume（with Claude Artifacts)

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns ai resume（with claude artifacts). Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

步骤1：收集原始信息

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns 步骤1：收集原始信息. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

步骤2：提炼简历信息

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns 步骤2：提炼简历信息. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

任务

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns 任务. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

技术实现

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns 技术实现. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

工作流：

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns 工作流：. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

system prompt and tools from claude code

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns system prompt and tools from claude code. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Summarize this PDF document (official example)

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns summarize this pdf document (official example). Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Explain Python Code (official example)

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns explain python code (official example). Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

AutoGPT

Upstream treats this as a distinct part of langgptai/awesome-claude-prompts. In plain language, use this area when your task concerns autogpt. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

How to use the main workflows

1

Choose the smallest relevant function

Start with one capability card instead of asking the repository to do everything at once. This makes permissions, inputs, and output easier to understand.

2

Prepare a disposable input

Use a sample URL, copied repository, test document, or sandbox account. Keep production credentials and irreplaceable files out of the first run.

3

Run, observe, and stop

Watch Terminal output or the host application's activity view. If the behavior differs from the README, stop with Control + C or cancel inside the host before retrying.

4

Inspect the result

Check generated files, diffs, API responses, logs, or previews. Never assume “command finished” means the result is correct.

5

Save a repeatable recipe

Record the working command and non-secret configuration in your project's README. Store secrets in the documented environment file or password manager.

Copy-paste recipes from upstream documentation

These examples are selected from the repository's first-party documentation. Replace obvious placeholders, keep quotation marks intact, and run them only in the context indicated by the surrounding explanation.

Explain Python Code (official example)
I am reading code for a python game. Explain to me how it works.
Practice Spanish Vocab (official example)
Help me practice my Spanish vocab.

For every turn, message me with a single Spanish word that I should translate to English.

Start with a very easy word. If I get it right, make the next word more difficult. If I get it wrong, explain what the correct answer was, and reduce difficulty for the next turn.

You can include emoji hints to help me.
Handle sales calls using AI
I need you to build a conversation between two people; one is John and the other is Robert.

[outline a scenario how you want between the persons]

Now show exactly how this conversation goes from start to end, and after every objection handled by Robert, show which framework Robert used to convince John's objections.

Configuration, accounts, and files

Configuration files

None documented

A configuration file changes behavior without changing source code. Make one change at a time and keep a backup before editing JSON, TOML, YAML, or environment files.

Important directories

None documented

Paths identify where the relevant implementation or generated files live. Paths beginning with ~ are inside your home folder.

Credentials

None documented

Prefer temporary, least-privileged credentials. Never commit .env, tokens, cookies, private keys, or session exports.

External services

None documented

Check pricing, data retention, rate limits, and account permissions before enabling optional integrations.

Safe operating habits

  • Use test data first and keep a current backup or Git commit.
  • Read commands before pasting. A README is useful evidence, not a substitute for judgment.
  • Review agent-generated file changes with git diff before committing.
  • Keep local services bound to 127.0.0.1 unless you intentionally secure and expose them.
  • Do not give plugins or MCP servers broader filesystem, browser, GitHub, or cloud access than their current task requires.
  • Confirm API costs and model names before running large batches.
  • Stop and investigate repeated authentication failures instead of pasting a token into multiple places.

Reference and source trail

The manual reflects first-party files checked on August 18, 2026. It explains the indexed repository rather than promising that every optional third-party integration is available or safe.