Weeexiao/crowdScaleShorts

Absurd Crowd Shorts Series

Core concept: Familiar location × Absurd crowd size × A daily goal × Causal escalation × Twist ending. The crowd size is a condition that creates consequences, not a number that must be shown in every shot.

1. Determine the Current Phase

First, identify whether the user wants reference analysis, topic selection, a single script, series planning, or actual video production. Only complete the specified phase; building a skill does not equal authorization to generate videos or publish works.

Follow the user's given style, duration, protagonist, and tools. If missing, initially conceptualize with a 60–90 second vertical adjustable plan, but do not treat defaults as user requirements. Clearly note when the user says "what if" and preserve their formal series title.

2. Analyze References and Avoid Redundancy

When reference videos exist, actually read the video metadata, sample frames, and any obtainable dialogue; do not just repeat the file name. Read references/referenceAnalysis.md. Separate observed facts, estimated timing, and creative inferences. Do not fabricate content not seen or heard. Do not claim entire track popularity, traffic, or commercial results based on a single reference.

Maintain a used list: location, crowd size, protagonist goal, obstacle, escalation method, core visuals, ending. If the user identifies an existing theme, immediately add it to the disallowed candidates; even if the current sample does not show it, defer to the user's supplementary input.

Changing numbers, location names, or character names does not count as original difference. A new plan must at least alter the core life task, the obstacle caused by the crowd, and the ending mechanism; check whether it still reuses the original video's signature gags. Learn the structure, do not copy characters, lines, specific shots, or advertisements.

3. Topic Selection

Default to providing 3–5 clearly differentiated candidates, not a large list of empty titles. Each candidate includes: location, crowd size, daily goal, how the crowd obstructs the goal, three layers of consequences, twist ending, and reusable production assets.

Filter with three questions:

1. Without the exaggerated crowd, does this conflict still work? If it fully works, the crowd is just decoration.
2. Would the audience be familiar with this small thing, and can they understand the protagonist's goal in one sentence?
3. Can it naturally lead to three different kinds of consequences, rather than just making a line longer?

Crowd size does not have to increase each episode; choose a scale sufficient to change the rules of life and be visually understandable. Do not chase more zeros.

4. Rules, Characters, and Escalation

Start each episode with one world rule and one protagonist goal. Only amplify one core condition; other behaviors should follow everyday logic. Absurd consequences can be unscientific but must obey the same in-universe rules.

Protagonists bear the audience perspective; supporting characters can be rule-enforcers who take the absurdity in stride. The protagonist's shock contrasted with others' calm creates stronger dissonance than everyone shouting. Series can reuse fixed protagonists and a few supporting characters, but do not default to copying the reference actor's face or voice.

Escalation dimensions can include time, distance, stamina, resources, management, communication, or collective behavior. Try to change escalation dimensions between adjacent gags, but all changes still serve the same goal.

Avoid humor based on harming or humiliating specific identity groups, or replacing laughter with irrelevant grossness. Dangerous behavior may be presented as surreal exaggeration, but do not provide realistic instructions for imitation.

5. Single Episode Structure

Allocate duration as needed, without mechanically applying fixed seconds:

1. Scale spectacle + a very ordinary life request.
2. First obstacle, letting the audience accept the world rule.
3. Two to three causal escalations, with the character's cost gradually changing.
4. False resolution, giving the protagonist a brief relief.
5. The final blow from the same rule, ending with the character's reaction.

Each gag should ideally have a "visible cause → result → reaction." Time subtitles can compress repetitive processes but cannot replace all visual action. Clarify which gags are dialogue-based and which must rely on composition or editing.

When writing dialogue, have characters pursue their own goals, not narrate the setting; explain rules through casual lines, avoiding long monologues. Do not make every line a shout or internet meme.

6. AI Storyboarding and Series Assets

When the user requires a production plan, read references/productionWorkflow.md. A few wide shots establish crowd scale; medium close-ups carry performance; local props or off-screen sounds supplement scale. Important crowd actions must be genuinely visible, not replaced by vague background filling in for key plot evidence.

Each generated segment must specify unique location, character positions, action, camera position, shot type, movement, dialogue, and sound source. Plan crowd wide shots and protagonist performance separately to avoid requiring the model to stably control many independent characters simultaneously.

Default to no product placement. When the user requests commercial integration, involve the product in the task or consequence chain, and do not fabricate its efficacy, price, or platform service promises. Mark the pacing cost of ad segments separately.

7. Output and Review

Output reference deconstruction, candidate list, series setting table, story beats, or shot-by-shot script based on the phase. Complete scripts can use references/episodeTemplate.md.

Before delivery, check item by item: the setting is instantly understandable; the protagonist has one clear goal; the crowd size indeed causes conflict; escalation does not repeat; the ending is derived from established rules; disallowed themes and signature gags are not reused; shots can actually be generated; duration allocation is feasible.

When the user only requests planning, do not generate media, create projects, or submit paid tasks. Only call available tools after the user authorizes production, proceeding within their approved scope. Installation and usage details can be found in README.md.