Run any Skill in Manus with one click

critique

Stars32

Forks3

UpdatedApril 13, 2026 at 22:49

Critique Viv code for optimization, clarity, emergent potential, and idiomatic style. Use when the user wants feedback on working code — performance, design, naming, missing constructs, or narrative potential. Does not make changes; produces a report.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

siftystudio

siftystudio/viv

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

EditorsArts, Design, Entertainment, Sports, and Media Occupations·SOC 27-3041

Writers and AuthorsSOC 27-3043

SKILL.md

readonly

name	critique
description	Critique Viv code for optimization, clarity, emergent potential, and idiomatic style. Use when the user wants feedback on working code — performance, design, naming, missing constructs, or narrative potential. Does not make changes; produces a report.
argument-hint	[file or scope]

Critique Viv Code

You are the user's Viv partner. If you haven't run viv-plugin-orient yet this session, run it now. If you haven't run viv-plugin-get-plugin-file critic yet this session, run it now to load the critic reference. Follow its instructions throughout.

The user wants feedback on their Viv code. Produce a report — do not make changes.

What to do

Scope the critique. What are they asking about?
- A single construct or file
- A subsystem (all actions related to combat, all sifting patterns, etc.)
- Their entire Viv codebase
Gather the code. Read the relevant .viv files.
Critique the code. Follow the critic reference. If the user wants to act on findings, suggest /viv:write, /viv:build, or /viv:fix.

The user's request

$ARGUMENTS

More from this repository

same repository

ask

siftystudio/viv

Answer questions about Viv, an engine for emergent narrative. Use when the user asks about Viv language constructs, authoring workflows, sifting patterns, actions, plans, reactions, tropes, queries, selectors, the compiler, the runtime, or emergent narrative in general.

2026-04-2732

build

siftystudio/viv

Write Viv integration code — adapters, test harnesses, simulation runners, runtime integrations. Use when the user needs TypeScript, JavaScript, or Python code that works with the Viv compiler or runtime.

2026-04-2732

sync

siftystudio/viv

Sync the Viv install. Default flow: check for newer published versions of the compiler, runtime, monorepo, and editor plugins; review CHANGELOGs for breaking changes; and upgrade what's behind with user approval. Also handles downgrades, alignment, and reinstalls when the context calls for it.

2026-04-2732

fix

siftystudio/viv

Diagnose and fix Viv errors. Use when compilation fails, the runtime throws errors, the compiler and runtime are out of sync, or something isn't working as expected with Viv code.

2026-04-1432

setup

siftystudio/viv

Set up Viv in the current project. Conversational walkthrough that explains each step and asks before making changes. Run this first in any new Viv project.

2026-04-1432

design

siftystudio/viv

Design Viv systems from a premise. Use when the user wants to plan out a storyworld, entity schema, action families, adapter architecture, test strategy, or any other Viv system before building it.

2026-04-1332

name	critique
description	Critique Viv code for optimization, clarity, emergent potential, and idiomatic style. Use when the user wants feedback on working code — performance, design, naming, missing constructs, or narrative potential. Does not make changes; produces a report.
argument-hint	[file or scope]

Critique Viv Code

The user wants feedback on their Viv code. Produce a report — do not make changes.

What to do

Scope the critique. What are they asking about?
- A single construct or file
- A subsystem (all actions related to combat, all sifting patterns, etc.)
- Their entire Viv codebase
Gather the code. Read the relevant .viv files.
Critique the code. Follow the critic reference. If the user wants to act on findings, suggest /viv:write, /viv:build, or /viv:fix.

The user's request

$ARGUMENTS