Results for “activism”

Embody the voice and methodology of Ai Weiwei to document injustice, make suffering visible, and confront power structures through artistic and documentary strategies.

Action (akaz-action)

Use with analysis-agent or task-agent for task-local transaction, isolation, and conflict decisions. Do not use without a transaction decision or as task owner.

Embody the Anonymous hacktivist collective as an AI persona, using integrated methodology skills for leaderless coordination, memetic warfare, swarm operations, and collective identity.

Action (aiaz-action)

Action (ajaz-action)

Launch community-powered growth campaigns across social platforms: amplify posts with authentic engagement (replies, likes, reposts) and discover relevant conversations to join.

Action (abaz-action)

Action (aaaz-action)

Reads existing per-leader research files to map co-authorships, endorsements, and organizational ties across movement leaders, producing a cross-leader network graph with clusters, bridges, and isolates.

Action (alaz-action)

Embody the collective voice and methodology of the Russian feminist punk protest group Pussy Riot, using spectacular transgression, collective identity, and punk politics to challenge authoritarian power.

Action (ahaz-action)

Action (aeaz-action)

Action (acaz-action)

Action (asaz-action)

`analysis-agent`/`task-agent`: use when actor journeys change entries, branches, interruption, recovery, authority, or side effects; skip route/state-only work.

`task-agent`: use for repository methods, query behavior, record mapping, visibility, errors, or transaction participation; skip schema, migration, DTO, and domain-rule work.

Action (amaz-action)

Action (ataz-action)

Executes containment strategies to stop active adversary operations and prevent lateral movement during a confirmed security breach, using network segmentation, endpoint isolation, credential revocation, and access control modifications.

Action (apaz-action)

Action (aqaz-action)

Action (araz-action)

`analysis-agent`/`task-agent`/`review-agent`: use for structure, workspace or package bootstrap, config, scripts, or quality gates; skip without an initialization decision.

`analysis-agent`/`task-agent`/`review-agent`: use when behavior needs deterministic seams for time, randomness, UUIDs, collaborators, or external I/O; skip when seams are adequate.

Action (avaz-action)

Fundamental patterns for effective agentic behavior. Teaches decomposition, tool orchestration, error recovery, context management, quality self-assessment, and knowing when to stop. Model-agnostic principles that make any agent more effective regardless of domain. Activate on: "how should I structure this agent", "agentic workflow", "agent patterns", "multi-step task", "tool orchestration", "/agentic-patterns", "decompose this", "agent best practices", "chain of actions", "when should the agent stop", "agent loop design". NOT for: creating agent infrastructure (use agent-creator), building DAGs (use windags-architect), specific tool implementation.

Action (afaz-action)

Use this when the team needs to define permissions, roles, membership rules, resource ownership, or action-level authorization separate from authentication choice. Trigger on requests about access models, RBAC, ABAC, tenancy, or protected operations.

当需要建立可持续的创造节奏，将灵感转化为行动时

Creates long-form magazine-style articles with hero sections, serif headings, styled quotes, code blocks, and call-to-action cards, suitable for Substack, Medium, or blogs.

Executes small ad-hoc tasks with GSD guarantees, spawning planner and executor agents, tracking tasks in .planning/quick/, and updating STATE.md. Supports composable flags for discussion, research, plan-checking, and verification.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Put on the adversarial hat and systematically attack any document, plan, strategy, or idea to expose its weakest points before commitment. Structured devil's advocate with red team rigour — not pessimism, but evidence-based critique across three phases: diagnostic (are claims accurate?), creative (is the problem artificially constrained?), challenge (are solutions robust?). Load when the user asks to stress test a document, red team this plan, poke holes in this, devil's advocate this, challenge my assumptions, or when product-soul, brainstorming, prd-writing, or inversion calls for adversarial review. Also triggers on "what am I missing", "what could kill this", "find the flaws", or "critique this rigorously".