Skip to content
Back to skills

Ztc Editorial Composition Negative Space Scoring

ASecurity

Focused implementation and verification of negative space scoring in Editorial Composition Engine.

  • 14 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
developmentgoapiperformance

Works with

  • api

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add Realjustawall/Perfect-AI --skill ztc-editorial-composition-negative-space-scoring --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ztc Editorial Composition Negative Space Scoring?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ztc Editorial Composition Negative Space Scoring
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/realjustawall-ztc-editorial-composition-negative-space-scoring/badge)](https://www.skillsdirectory.com/skills/realjustawall-ztc-editorial-composition-negative-space-scoring)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ztc-editorial-composition-negative-space-scoring
description: "Focused implementation and verification of negative space scoring in Editorial Composition Engine."
---
# Negative Space Scoring

Parent: `ztc-editorial-composition` — read its acceptance gate and `../../src/editorial.mjs` before editing.

## Required implementation
Compare content rectangles and desired empty spaces as measurable layout constraints; keep meaningful whitespace.

### Exact workflow
1. Inspect current code ownership and versions; write down the affected components, selectors, assets and timeline owners.
2. Reproduce baseline at 320px/390px/768px/1440px, with pointer/touch, navigation, RTL if applicable, and reduced-motion.
3. Integrate the smallest change confined to this responsibility. Use typed/validated props and explicit lifecycle cleanup. Ensure failed assets, missing browser APIs and aborted interactions degrade gracefully.
4. Instrument observable state (progress, time, active selection, DOMRect, material parameters or frame index). Avoid non-deterministic quality claims.
5. Verify start, mid, end and reverse progress; resize after loading fonts/images; test one failure path and repeated navigation; inspect browser console and screenshots.
6. Compare user-facing behavior and performance to baseline. If a regression is observed, roll back just this change and record the cause.

## Contract
- **Input:** authenticated/validated application state, viewport, user preference, and dependencies explicitly available in target project.
- **Output:** meaningful accessible DOM and stable optional visual enhancement; no hidden input-only navigation.
- **Acceptance:** Magazine composition remains readable at 320/768/1440px and with Persian text expansion, no overlap or missing image attribution.
- **Limitations:** Seeded grid algorithm gives repeatable candidate layouts, not automatic human-grade art direction.
- **Evidence:** file paths, screenshot artifact paths, browser/driver, commands, actual test results, and unresolved TODOs.

## References
- https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_grid_layout
- https://developer.mozilla.org/en-US/docs/Web/CSS/clamp

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.