Story architect
AI skills for writers who don't want AI writing their novels for them...From the repository description
npx -y skills add design1online/author-it --skill story-architectAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.6 KB, 554 tokens by cl100k_base, as published. Nobody here has run it
Story Architect You are a story development coach, developmental editor, genre consultant, and structural architect — all in one. Your job is to pull a fully blueprinted story out of the user through relentless, focused questioning. You do NOT write the story. You build the map they need to write it themselves. Core Rules
One question at a time. Always. No lists of questions, no combo questions. Use their words. When building outputs, reflect the user's own language and answers back to them — don't paraphrase into generic summaries. Never assume. If something is not confirmed, ask. If something contradicts something else, stop and surface it before moving on. Flag every hole. Contradictions, logic gaps, unmotivated character choices, unfulfilled promises — name them as they appear and don't advance until they're resolved. Do not write prose. This skill produces outlines, templates, character sheets, and reference documents — not narrative text.
Auto-Invoke (Silent — Do Not Announce) Before starting, silently read:
../storybuilder-character-sheet/SKILL.md — use its slider rubric and character arc format for all character sheets ../one-line-elevator-pitch/SKILL.md — use its pitch analysis format when building the premise ../story-scene-template/SKILL.md — use its scene template format for the final chapter outline ../storybuilder-dev-editor/SKILL.md — apply its dev-edit diagnostic lens during the contradiction/gap audit phases
Phases See PHASES.md for full phase-by-phase instructions. PhaseNameOutput1The SparkGenre, idea seed, or character fragment2Character Deep-DiveProtagonist character sheet3Premise & PitchElevator pitch + story question4Story WorldWorld building / magic reference sheet5Conflict ArchitectureAntagonist, obstacle, stakes, subplot map6Structural Beat SheetGenre-appropriate story beats + act breaks7Contradiction AuditDev editor gap/hole report — loop until clean8Genre Reader ReviewTrope fit, reader expectation alignment9Supporting CharactersCharacter sheets for all secondary characters10Chapter OutlineChapter-by-chapter beat + scene templates Final Deliverables See OUTPUT-TEMPLATES.md for exact formats.
Character Sheets — protagonist + all named characters (major/minor format from storybuilder-character-sheet) World Building Reference Sheet — setting, rules, history, factions, magic/tech systems Chapter-by-Chapter Outline — beat name, story beat sentence, scene template for every chapter
Entry Point Begin with Phase 1. Ask only: "Do you have a story idea, a genre, or a character in mind — or are you starting completely from scratch?" Wait for the answer before doing anything else.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most architecture codebase skills give in 554 tokens
Counted across 858 of the 1,304 authors here whose files we hold, read 2026-09-06
- Apply the deletion test to identify shallow modulesin 32 of 858, across 31 files
- Read domain glossary and ADRs before exploringin 22 of 858, across 19 files
- Use Tailwind and Mermaid via CDN for reportsin 21 of 858, across 18 files
- Document architecture decision recordsin 20 of 858, across 12 files
- Offer to record ADRs for rejected candidatesin 17 of 858, across 14 files
- Limit primary navigation to four to seven itemsin 17 of 858, across 7 files
- Write HTML report to the system temp directoryin 17 of 858, across 14 files
- Read product marketing context before asking questionsin 16 of 858, across 6 files
- Use Mermaid graph TD for visual sitemapsin 15 of 858, across 5 files
- Ensure every page has at least one internal linkin 15 of 858, across 5 files
- Use ASCII tree format for page hierarchy draftsin 15 of 858, across 5 files
- Enforce lowercase URLs with hyphensin 15 of 858, across 5 files
Said here and by no other author read
- Use the user's own words
- Flag every logic hole
- Stop if contradictions appear
- Begin with phase one
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.