基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/aibot88/sec_skill_store --skill scene-beat命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Guía técnica completa para integrar 250+ servicios externos con agentes IA usando Composio. Cubre instalación, autenticación OAuth, gestión de herramientas, triggers y flujos multi-servicio.
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project
| name | scene-beat |
| description | Structure individual scenes using Scene-Sequel framework with goal-conflict-disaster beats |
Use this skill when the user needs help structuring an individual scene with proper dramatic beats.
The character pursues a goal
Goal → Conflict → Disaster
The character processes the disaster
Reaction → Dilemma → Decision
This creates a cycle: Scene → Sequel → Scene → Sequel
What the character wants RIGHT NOW
Requirements:
Examples:
What prevents easy success
Types of Obstacles:
Requirements:
How it goes WORSE than expected
NOT the same as failure!
Disaster Types:
Requirements:
Immediate emotional response
Show the human moment:
Duration: Short (1-2 paragraphs usually)
Analyzing the bad options
All choices have downsides:
This is where character depth shows
Choosing the least bad option
This becomes the GOAL of the next scene
Ask the user:
What type of scene is this?
1. Action Scene (physical conflict, chase, fight)
2. Dialogue Scene (negotiation, argument, revelation)
3. Discovery Scene (finding evidence, learning truth)
4. Relationship Scene (emotional connection, conflict)
5. Planning Scene (characters strategize)
6. Transition Scene (character travels, prepares)
Help user define the scene goal:
## Define the Scene Goal
**Current situation**: Protagonist just learned their partner is lying
**What does protagonist want in THIS scene?**
(Choose one or suggest another)
A. Confront partner and demand truth
B. Gather more evidence before confronting
C. Confide in someone else for advice
D. Custom: ___________
**Why this goal?** (helps establish character motivation)
Once goal is defined, generate full scene beats:
## Scene Beat Sheet
### SCENE: Confrontation at the Apartment
**Setting**: Partner's apartment, late evening, protagonist unexpected visit
---
#### Beat 1: GOAL
Confront partner about the lie and get the truth
**Opening Line Suggestion**:
"We need to talk. And this time, I want the real story."
**Goal Clarity**:
- Specific: Yes (get truth about specific lie)
- Measurable: Yes (either they confess or don't)
- Time-bound: Yes (happens in this conversation)
- Stakes: High (relationship depends on it)
---
#### Beat 2: CONFLICT (3 escalating obstacles)
**Obstacle 1: Denial**
Partner denies everything. "I don't know what you're talking about."
- Protagonist must present evidence
- Tension: Partner is convincing, makes protagonist doubt own judgment
**Obstacle 2: Deflection**
Partner turns it around. "Why are you accusing me? Don't you trust me?"
- Now protagonist is on defensive
- Tension: Protagonist's flaw (fear of being wrong) activated
**Obstacle 3: Partial Truth**
Partner admits to minor lie but not the major one
- "Okay, yes, I was at the office late, but that's ALL that happened"
- Protagonist senses there's more but can't prove it
- Partner is getting defensive/angry
**Peak Tension**:
Protagonist must decide: Push harder (risk blowup) or back down (accept lies)?
---
#### Beat 3: DISASTER (Yes, But)
**What Happens**:
Protagonist pushes one more time → Partner breaks down crying → Confesses everything
**BUT**:
"I did it to protect you. You can't tell anyone, or we're both in danger."
**New Problem Created**:
- Goal achieved (got truth)
- BUT now protagonist is complicit/in danger
- AND must decide whether to act on this truth or stay silent
- Stakes just multiplied
**Sequel Setup**:
Protagonist must now grapple with moral dilemma (internal conflict in sequel)
---
: Protagonist's car, sitting in parking lot after leaving apartment
---
Protagonist sits in stunned silence. Hands shaking on steering wheel. Mind racing. Can't believe what they just heard.
: Shock → Anger → Fear → Confusion
:
Breathing heavy
Can't turn key (hands trembling)
Sees their reflection in rearview mirror - doesn't recognize self
: 2-3 paragraphs
---
Protagonist weighs the terrible options:
Pros: Right thing to do, justice served, clean conscience
Cons: Partner goes to jail, protagonist implicated, danger becomes real
Pros: Keep partner safe, avoid danger, relationship survives
Cons: Betray own values, become accomplice, guilt forever
Pros: Go to the source, maybe resolve without authorities
Cons: Unknown danger, could make things worse, no backup
---
Protagonist makes a choice:
: Confront the source (Option C)
: Can't live with silence (value: truth) but can't destroy partner (value: loyalty)
: "If I can fix this at the source, maybe nobody has to get hurt"
: Protagonist knows this is risky but sees no other way. Grips the photo evidence. Starts car.
---
: Protagonist drives into the night, toward danger, toward truth, toward inevitable catastrophe
:
What will they find at the source?
Will the source be hostile or cooperative?
Is protagonist walking into a trap?
After structuring, evaluate:
## Scene Quality Check
**Goal**:
- [ ] Is it specific and measurable?
- [ ] Can we achieve it in one scene?
- [ ] Do we care if character succeeds?
**Conflict**:
- [ ] Does tension escalate (not stay flat)?
- [ ] Are obstacles believable?
- [ ] Does conflict test character's flaw/strength?
**Disaster**:
- [ ] Is it worse than expected?
- [ ] Does it force a new decision?
- [ ] Will it surprise the reader?
**Sequel**:
- [ ] Is emotional reaction shown (not told)?
- [ ] Are all options bad in different ways?
- [ ] Does decision lead to new scene goal?
**Overall**:
- [ ] Does scene advance plot OR character arc?
- [ ] Is there a clear before/after?
- [ ] Does it hook to next scene?
## Scene Purpose
Every scene must do at least ONE of:
1. ✅ **Advance Plot** - New information, event, or action
2. ✅ **Develop Character** - Reveal trait, test flaw, show growth
3. ✅ **Explore Theme** - Illustrate story's central idea
4. ✅ **Build Relationship** - Change dynamic between characters
5. ✅ **World-building** - Reveal setting/culture/system
**Your Scene**:
- ✅ Advances Plot (reveals truth about partner)
- ✅ Develops Character (tests protagonist's values)
- ✅ Builds Relationship (changes partner dynamic)
**Score**: 3/5 purposes ✅ Strong scene
## Pacing Recommendation
**Recent scenes**:
- Chapter 5, Scene 1: Fast (action)
- Chapter 5, Scene 2: Fast (discovery)
- Chapter 6, Scene 1: Fast (confrontation)
**Pattern**: 3 fast scenes in a row
**Recommendation**: Make SEQUEL longer than usual
- Give reader breathing room
- Deepen emotional impact
- Build anticipation for next scene
**Sequel Target Length**: 500-800 words (instead of usual 200-300)
## Choosing the Right Disaster
**Context**: This is Scene 7 of 15 in Act 2
**Analysis**:
- Early Act 2: Use "Yes, But" disasters (partial progress)
- Mid Act 2: Use "No" disasters (setbacks)
- Late Act 2: Use "No, And Furthermore" (all seems lost)
**Recommendation**: "Yes, But" disaster
- Protagonist achieves scene goal (gets truth)
- BUT complications arise (complicity, danger)
- This maintains momentum while raising stakes
**Future Note**: Save "No, And Furthermore" for Scene 12 (approaching Act 2 climax)
## Chapter Structure: 3 Scenes
**Scene 1**: Protagonist gathers evidence (Scene)
**Scene 2**: Protagonist processes what evidence means (Sequel)
**Scene 3**: Protagonist confronts partner (Scene)
**Problem**: Two action scenes with one sequel creates exhausting pace
**Recommendation**: Restructure as:
**Scene 1**: Gather evidence (Scene)
**Scene 2**: Process evidence + Make plan (Sequel/Transition)
**Scene 3**: Confrontation Part 1 - Denial (Scene, ends in Disaster)
**Scene 4**: Brief reaction + New tactic (Short Sequel)
**Scene 5**: Confrontation Part 2 - Confession (Scene)
Now: 3 Scenes + 2 Sequels = Better rhythm
Symptom: Characters just talk/act without purpose Fix: Add "What does protagonist want RIGHT NOW?"
Symptom: Protagonist achieves goal on first try Fix: Add 2-3 escalating obstacles before disaster
Symptom: Protagonist gets what they want, scene feels flat Fix: Change to "Yes, But" or "No" disaster
Symptom: Character immediately knows what to do next Fix: Show genuine struggle in dilemma phase
Symptom: Next scene starts with different goal Fix: Make decision the explicit goal of next scene
Scene beats map to Shuangdian patterns:
## Shuangdian Opportunities in Scene Beats
**GOAL Phase**:
- MAS patterns (protagonist shows competence)
- UPG patterns (protagonist learns new skill)
**CONFLICT Phase**:
- CRI patterns (high-stakes tension)
- FOR patterns (boundary-breaking)
- CHO patterns (spiraling chaos)
**DISASTER Phase**:
- REV patterns (if disaster is actually secret victory)
- DOM patterns (if protagonist dominates despite disaster)
- CAT patterns (if disaster is meaningful suffering)
**SEQUEL Phase**:
- HEA patterns (emotional understanding)
- PHI patterns (existential reflection)
- RES patterns (collective emotional moment)
**Use** `/shuangdian-next` **to identify specific patterns for each beat**
User: I need to write a scene where my character searches for evidence
/scene-beat
[Skill structures the scene]
- Goal: Find the murder weapon
- Conflict: Warehouse is huge, time limit, security shows up
- Disaster: Finds weapon BUT it implicates their friend
User: Perfect, now help me write it
[Use regular AI generation with scene structure as guide]
User: This scene feels boring but I don't know why
[Pastes scene]
/scene-beat
[Skill analyzes scene]
Problem detected: No clear goal - character just reacts to events
Fix: Add specific goal at start, restructure obstacles
[Provides revised beat sheet]
User: I have 3 scenes in this chapter, help me structure them
/scene-beat --multiple
[Skill structures all 3 scenes as Scene-Sequel-Scene pattern]
- Ensures proper pacing
- Connects disasters to new goals
- Validates chapter arc
/plot-next - Macro level (whole story)/scene-beat - Micro level (individual scenes)/conflict-next - Focuses on conflict types/shuangdian-next - Identifies satisfaction moments in beatsSkill Status: ✅ Ready for use Framework: Scene-Sequel (Dwight Swain) Output: Complete beat-by-beat scene structure with examples