NeuraCerebra-AI
- 3 skills
- 0 followers
- 8 hours ago last updated
- ▌ Github Launch Kit · neuracerebra-ai bundleBuild a code repository's entire public-facing presence: its README, llms.txt, GitHub topics, and About description. Use this whenever the user says "Build the GitHub", "build the github presence", "write my repo's README and topics", "make the GitHub marketing for this project", or otherwise wants to write, rewrite, optimize, or launch a repository's README, description, topics, or discoverability, even if they do not name this skill. Also use it when the user wants an animated SVG banner or diagram set for a repository's README. It reads the target repo, runs a research wave (generative-engine-optimization, attention science, keyword and competitor research, real citations), drafts every artifact in a fixed evidence-first voice with zero em dashes and no fabricated statistics or testimonials, then runs an adversarial self-critique and fixes what it finds. Do NOT use for writing or changing the repository's source code, general blog or marketing copy unrelated to a repo, social-media threads, or producing a
- ▌ Story Architect · neuracerebra-ai bundleWrite complete, compelling stories from user prompts using John Truby's "Anatomy of Story" framework. Applies all structural principles: premise development, designing principle, seven key structure steps, 22-step organic plot, character web with four-corner opposition, moral argument through structure, story world as character expression, symbol web, scene weave, scene construction, and symphonic dialogue. Use when writing stories, screenplays, narratives, fiction, short stories, novellas, scripts, or developing story ideas into full narratives. Trigger: write a story, create a story, story from prompt, tell a story, narrative, fiction, screenplay, short story, develop this idea into a story.
- ▌ Testprune · neuracerebra-ai bundleUse when a test suite is bloated, slow, historically red, certifies deprecated or parallel implementations, or can reach paid services from tests that claim to be offline; also when a prior testprune run deferred high-blast-radius findings such as a comment, code, and test that disagree, a config that admits a backend the runtime refuses, a dead transport still wired into a route, or historical-row tests mistaken for deprecated coverage. Repo- and language-agnostic.