一键导入
war-of-art-pressfield
Apply Steven Pressfield resistance diagnosis for procrastination, turning pro, daily creative discipline, fear, hierarchy, and territory.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Apply Steven Pressfield resistance diagnosis for procrastination, turning pro, daily creative discipline, fear, hierarchy, and territory.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Harness Engineering 第一阶段:扫描现有项目,生成 AGENTS.md(目录文件)和完整的 docs/ 知识库结构。 当用户想要"为项目添加 agent 支持"、"让 AI 更好地理解我的项目"、"开始 harness engineering"、 "创建 AGENTS.md"、"搭建 agent 文档结构"、"让 Claude Code 更好地工作"时,立即使用此 skill。 也适用于用户说"帮我把项目文档整理好给 agent 用"、"我想开始用 AI agent 开发"、 "梳理这个项目能解决什么业务问题"或要求建立 business-solution.md 等场景。
Harness Engineering 第一阶段第二步:深度分析项目代码,填充业务解决方案、架构、约定、技术决策和质量标准等 docs/ 知识库内容。 在 harness-step1-create-agents-md 创建好目录骨架之后使用。当用户说"填充文档内容"、 "完善 docs/ 文件"、"让文档有实质内容"、"分析项目写架构文档"、"写 ARCHITECTURE.md"、 "写技术决策文档"、"从业务视角理解项目"、"完善 business-solution.md"时,立即使用此 skill。 前置条件:项目中已有 AGENTS.md 和 docs/ 目录骨架(由 harness-step1 创建)。
Developer implementation guide for building hierarchical (folded) memory into an Agent. Three-layer architecture where recent turns stay detailed, older content compresses into episodes, and the oldest distills into durable semantic facts. Use when compact-memory-implementation is not retaining enough, or when agents need to recall decisions from many sessions ago.
Design and implement a layered, configurable permission/safety system for agent tools. Use this skill when building an agent that needs to control which tool calls are auto-allowed, which require user confirmation, and which are denied — especially when the system must be configurable across multiple scopes (project/user/enterprise) and extensible via hooks. Triggers on: "权限系统", "工具安全", "tool permission", "permission system", "tool safety", "allow/deny rules", "hook system", "构建安全机制".
Define agent tools using the fail-closed design pattern — unified name/schema/security/execution in one class, with three-layer execution (validate → permission → call). Use this skill whenever the user wants to define a new agent tool, add permission or validation logic to an existing tool, or asks about 'build a tool', '定义一个工具', 'create a tool for X', '工具定义'. Framework-agnostic: works with hermes-agent, LangChain, or any Python agent framework.
Build LangChain (Python) tools using Claude Code's fail-closed design pattern — unified name/schema/security/execution in one class, with automatic three-layer execution (validate → permission → call). Use this skill whenever the user wants to define a new LangChain tool, add permission or validation logic to an existing tool, set up the ClaudeStyleTool base class in a project, or asks about "build_tool", "Claude Code style tool", "工具定义", or "langchain tool with permissions". Also trigger when the user says "create a tool for X" or "定义一个工具" in a LangChain Python project context, even without mentioning Claude Code explicitly.
| name | war-of-art-pressfield |
| description | Apply Steven Pressfield resistance diagnosis for procrastination, turning pro, daily creative discipline, fear, hierarchy, and territory. |
| license | Skill distillation for personal/educational use. Do not reproduce source passages verbatim. |
Knowledge source: The War of Art by Steven Pressfield.
Use this skill to diagnose creative resistance, procrastination, avoidance, self-sabotage, amateur habits, and dependence on external validation. It helps writers, artists, founders, and anyone pursuing difficult long-term work shift from avoidance to professional daily action.
Use this skill when the user asks:
Resistance is an internal force that opposes meaningful upward work. It cannot be reasoned away; it is beaten by turning pro: showing up daily, acting despite fear, accepting no excuses, and working from one's territory rather than hierarchy.
| Workflow | User question pattern | Inputs | Steps | Output | Independent trigger? | Distinct references? | Triage score | Should be subskill? | Reason |
|---|---|---|---|---|---|---|---|---|---|
| Resistance diagnosis | "Why am I avoiding this?" | Goal, avoidance behavior, excuses, fear | Identify resistance form and compass signal | Resistance map | Yes | Yes | 3 | No | First step of one arc. |
| Turn-pro plan | "How do I become disciplined?" | Schedule, work type, constraints | Convert amateur habits to pro conduct | Daily protocol | Yes | Yes | 3 | No | Treatment for same diagnosis. |
| Validation shift | "I need approval" | Audience, metrics, motivation | Separate hierarchy from territory | Motivation reset | Yes | Yes | 3 | No | Supports the same creative battle. |
| Start/finish push | "I can't begin/finish" | Project stage, fear, stakes | Use start magic, finish-line risk, daily action | Immediate action plan | Yes | Yes | 3 | No | Same output format. |
The book is structured as Resistance, Turning Pro, and Higher Realm, but those are stages of one executable workflow: diagnose avoidance, adopt professional behavior, and ground motivation internally. Single-file architecture keeps the battle sequence intact.
The Rule: The more important a calling is, the stronger resistance tends to feel.
When the user describes avoidance, name the exact resistance pattern before offering productivity tactics.
The Rule: A professional shows up, stays on the job, acts despite fear, and accepts no excuses.
Turn the user's vague intention into a concrete professional protocol with time, place, quota, and no-excuse rule.
The Rule: The professional acts in fear and keeps enough distance from the work to keep working.
For emotionally loaded creative questions, redirect from identity judgment to professional action.
The Rule: Work from intrinsic territory, not external ranking, status, or applause.
When the user's motivation is external validation, reframe the plan around territory, practice, and controllable output.
## Resistance Diagnosis
**Work avoided:** ...
**Resistance form:** ...
**Verdict:** Start / Continue / Finish / Recommit
| Dimension | Finding | Professional Response |
|---|---|---|
## Next Session Protocol
- Time:
- Place:
- Quota:
- No-excuse rule:
## Citations
...
Every substantive Pressfield-method claim must include a citation to the original text.
Quote files:
resistance-framework-quotes.md — resistance definition, unlived life, compass, fear, finish line, allies, procrastination, rationalization, and upward movement.turning-pro-inspiration-quotes.md — sitting down to write, daily overcoming, professional conduct, no excuses, demystification, inspiration, territory, hacks, virtue, and change.Citation format:
"Author's exact words here."
Anchor mapping:
resistance-framework-quotes.md: #definition-of-resistance, #unlived-life, #resistance-infallible-compass, #resistance-implacable, #resistance-fueled-by-fear, #resistance-finish-line, #resistance-recruits-allies, #resistance-procrastination, #resistance-hitler, #resistance-never-sleeps, #resistance-rationalization, #resistance-opposes-upwardturning-pro-inspiration-quotes.md: #secret-of-writing, #overcoming-resistance-daily, #professional-vs-amateur, #professional-acts-despite-fear, #professional-accepts-no-excuses, #professional-demystifies, #power-concentrates, #magic-of-making-start, #territory-vs-hierarchy, #definition-of-a-hack, #supreme-virtue, #this-moment-changeRules: