원클릭으로 Manus에서 모든 스킬 실행

시작하기

tersify

스타8

포크0

업데이트2026년 7월 11일 04:06

Simplify comments and tighten naming in the given files

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Anoptic-Games

Anoptic-Games/anoptic-engine

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

소프트웨어 개발자컴퓨터 및 수학직·SOC 15-1252

SKILL.md

readonly

name	tersify
description	Simplify comments and tighten naming in the given files
argument-hint	[files or module]

Simplify the FUCK out of the comments in $ARGUMENTS. Terisfy should always preserve semantic meaning.

Rationale comments die:

Comments say WHAT, never WHY. One line. eg: "# Sanitizer flags".
Preserving meaning means the what. The why is disposable.
Delete justification, design history, and alternatives-considered. "because", "so that", "previously", "not X because Y" are kill signals.
A policy paragraph -> its one-line conclusion. eg: 13 lines of build philosophy -> "# Build policy: whole builds, ThinLTO Release, modern linkers, static linking."
Inline comments are a bare noun. eg: shaderc # glslc
Usage hints survive because they are a what. eg: "# Override with: set MSYS2_CLANG=..."
Build files count: CMakeLists.txt, flake.nix, build.sh, build.bat.

Comments:

Decorated banners (# ---- Section ----) -> keep. If many comments cut in file, place new banners where logical. Clearly distinguishable visual blocks > pararaphs of loose comments.
One clause each. Cut dragging run-on sentences down to their meaning.
A comment needing paragraphs means the code is unclear. Rename a local instead.
No ; - -- — sentence-splitters. Needing one means it's too long, so cut it. Arrows (a -> b) ok.
Use the shorter synonym when a dev reads it identically. eg: "longest formatted line" --> "max formatted line"
Never allow comments to split mid-sentence. Make a newline or use /* */ for paragraphs.
Keep my /* Section */ banners and my own comments verbatim.
Conserve semantic meaning.

Naming, in src/ files:

Local variables are camelCase, eg: g_buf_len --> g_bufLen
Rename only where comments were doing a good name's work. Conservative, no behavior change. eg: p, m --> head, body

After: ./build.sh 5, run tests, show git diff --stat.

이 저장소의 다른 Skills

같은 저장소

coding-campaign

Anoptic-Games/anoptic-engine

A hierarchical GAN coder campaign. Run only when user mentions using Sol/Luna, claudex fleets, competing implementations, or architecture contests. The CMDR derives checkpointed operational phases from the ingested mission and advances them through fresh blind Opus supervisors; every code-bearing artifact is produced by claudex Sol/Luna Individual Units; supervisors only commission, judge, select, gate, and report.

2026-07-148

bench-fps

Anoptic-Games/anoptic-engine

Run the anopticengine FPS / GPU-pass benchmark and write the result to docs/benchmarks/. Use whenever asked to benchmark, run the sweep, measure frame throughput, or compare a shadow/render knob. Drives tools/perf/bench_fps_<platform>.py (win64 / linux / macos). NEVER invent a runner. Full methodology and every env knob live in tools/perf/bench_fps.md.

2026-07-128

create-test

Anoptic-Games/anoptic-engine

Create a test or benchmark in tests/ using the tests/templates primitives

2026-07-118

verify

Anoptic-Games/anoptic-engine

Drive an anoptic-engine change at its runtime surface — nix run to build+launch, screenshot-macos to capture, eval+substitution for Linux artifacts from a Mac.

2026-07-118

screenshot-macos

Anoptic-Games/anoptic-engine

Screenshot or visually inspect a running app's window on macOS (Darwin). ALWAYS use this whenever you need to see a native GUI on macOS — verify a rendered frame, confirm a visual change, capture any on-screen app. Runs .claude/tools/screenshot-macos (screencapture + CGWindowList). NEVER osascript / AppleScript / System Events.

2026-07-088

todostep

Anoptic-Games/anoptic-engine

Implement one step from the build sequence in docs/TODO.md

2026-06-248

name	tersify
description	Simplify comments and tighten naming in the given files
argument-hint	[files or module]

Simplify the FUCK out of the comments in $ARGUMENTS. Terisfy should always preserve semantic meaning.

Rationale comments die:

Comments say WHAT, never WHY. One line. eg: "# Sanitizer flags".
Preserving meaning means the what. The why is disposable.
Delete justification, design history, and alternatives-considered. "because", "so that", "previously", "not X because Y" are kill signals.
A policy paragraph -> its one-line conclusion. eg: 13 lines of build philosophy -> "# Build policy: whole builds, ThinLTO Release, modern linkers, static linking."
Inline comments are a bare noun. eg: shaderc # glslc
Usage hints survive because they are a what. eg: "# Override with: set MSYS2_CLANG=..."
Build files count: CMakeLists.txt, flake.nix, build.sh, build.bat.

Comments:

Decorated banners (# ---- Section ----) -> keep. If many comments cut in file, place new banners where logical. Clearly distinguishable visual blocks > pararaphs of loose comments.
One clause each. Cut dragging run-on sentences down to their meaning.
A comment needing paragraphs means the code is unclear. Rename a local instead.
No ; - -- — sentence-splitters. Needing one means it's too long, so cut it. Arrows (a -> b) ok.
Use the shorter synonym when a dev reads it identically. eg: "longest formatted line" --> "max formatted line"
Never allow comments to split mid-sentence. Make a newline or use /* */ for paragraphs.
Keep my /* Section */ banners and my own comments verbatim.
Conserve semantic meaning.

Naming, in src/ files:

Local variables are camelCase, eg: g_buf_len --> g_bufLen
Rename only where comments were doing a good name's work. Conservative, no behavior change. eg: p, m --> head, body

After: ./build.sh 5, run tests, show git diff --stat.