Verified:GitHub

pulse

Compress generated code while preserving identical behavior.

Updated Aug 27, 2026

Search Tags:#typescript #refactoring #code generation #implementation #token efficiency #coding guidelines #code compaction

Ready to run

npx skills add https://github.com/Z5Jonathan-maker/ai-coding-os --skill pulse-z5jonathan-maker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pulse
Source: https://github.com/Z5Jonathan-maker/ai-coding-os/tree/main/claude/skills/pulse
Command: npx skills add https://github.com/Z5Jonathan-maker/ai-coding-os --skill pulse-z5jonathan-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pulse solves wasted tokens and bloated implementations by making generated code significantly more compact while preserving identical behavior.

Core Features & Use Cases

Token-efficient code-density rules: Compresses code structure (guards, inlining, composition, idiomatic expressions) to reduce generated output size.
Session-level activation and intensity: Supports activation with lite/full/ultra to control how aggressively density is applied.
Pre-write and post-write compaction loop: Enforces planning (expected size, naming) and a cleanup pass (remove redundant comments/variables/imports/blank lines).

Quick Start

Ask your AI to switch to pulse mode and tighten the code for the current feature without changing its observable behavior.

Frequently Asked Questions about pulse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I reduce token bloat in generated TypeScript code?▼

You reduce code token bloat by applying density conventions: removing restating comments, using concise guards, inlining trivial extracts, and running a post-write compaction pass for unused imports and redundant formatting.

What is a post-write compaction pass for code generation?▼

A post-write compaction pass cleans up generated source code by removing unused imports, eliminating single-use temporaries, and stripping redundant formatting to ensure the final output remains dense and token-efficient.

How do I refactor code to be more token-efficient without changing behavior?▼

You refactor code for token efficiency by inlining trivial extracts, adopting idiomatic expressions, and avoiding unnecessary try/catch constructs, ensuring the refactored source maintains strictly identical observable behavior.

Can I control how aggressively code compaction is applied during implementation?▼

Yes, you can control code compaction aggressiveness using session-level activation intensities like lite, full, or ultra, which dictate how strictly density rules are enforced during feature implementation.

When should I avoid aggressive code density rules in source files?▼

You should avoid aggressive code density rules when generating source files that require extensive defensive programming, explicit try/catch error handling, or heavily documented comments for compliance and readability standards.