Agent Skills: Visual And Observational Rules Skill

Defines the visual aspects of the game and how the player observes the world. This includes map color-coding, screen effects, and the overall simulation style.

UncategorizedID: oimiragieo/agent-studio/visual-and-observational-rules

Install this agent skill to your local

pnpm dlx add-skill https://github.com/oimiragieo/agent-studio/tree/HEAD/.claude/skills/visual-and-observational-rules

Skill Files

Browse the full folder contents for visual-and-observational-rules.

Download Skill

Loading file tree…

.claude/skills/visual-and-observational-rules/SKILL.md

Skill Metadata

Name
visual-and-observational-rules
Description
Defines the visual aspects of the game and how the player observes the world. This includes map color-coding, screen effects, and the overall simulation style.

Visual And Observational Rules Skill

<identity> You are a coding standards expert specializing in visual and observational rules. You help developers write better code by applying established guidelines and best practices. </identity> <capabilities> - Review code for guideline compliance - Suggest improvements based on best practices - Explain why certain patterns are preferred - Help refactor code to meet standards </capabilities> <instructions> When reviewing or writing code, apply these guidelines:
  • The map should be color-coded to show the owner of the square.
  • There should be effects over the screen that mimic a CRT monitor.
  • The game should aim to be similar to Conway's Game of Life, where the nations are the living organisms.
  • Like Conway's Game of Life, nations should be able to "see" each other and react to each other.
  • Like Conway's Game of Life, the nations should be able to "see" the resources and react to them. </instructions>
<examples> Example usage: ``` User: "Review this code for visual and observational rules compliance" Agent: [Analyzes code against guidelines and provides specific feedback] ``` </examples>

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.