counterfact-generator-internals

Modify TypeScript generator internals and OpenAPI parsing while preserving regeneration guarantees.

169|19|Updated Apr 8, 2022
One-click install
npx skills add https://github.com/counterfact/api-simulator --skill counterfact-generator-internals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: counterfact-generator-internals
Source: https://github.com/counterfact/api-simulator/tree/main/.github/skills/counterfact-generator-internals
Command: npx skills add https://github.com/counterfact/api-simulator --skill counterfact-generator-internals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modify TypeScript generator internals, OpenAPI parsing/schema handling, and generated file writing behavior without regressing regeneration guarantees.

Core Features & Use Cases

  • Modify generator architecture across Specification/Requirement -> coders -> Script -> Repository.
  • Adjust OpenAPI loading, parsing, and type coders to support new features while preserving backward compatibility.
  • Ensure regeneration contracts are preserved when downstream changes occur, with predictable outputs and test coverage.

Quick Start

Implement a change to the TypeScript generator internals and run the generator test suite to ensure regeneration guarantees are preserved.

Frequently Asked Questions about counterfact-generator-internals

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

FAQPage Schema
How do I modify TypeScript generator internals without breaking regeneration guarantees?

Adjust OpenAPI parsing, schema handling, and generated file writing behavior across the Specification to Repository pipeline while preserving deterministic output and regeneration contracts.

What is the TypeScript generator architecture for OpenAPI schema handling?

The architecture flows from Specification and Requirement through coders to Script and Repository, coordinating OpenAPI loading, type coders, and file writing to produce deterministic generated outputs.

Can I change OpenAPI parsing behavior while keeping generated TypeScript outputs backward compatible?

Yes, you can adjust OpenAPI loading and type coders to support new features, provided changes maintain deterministic output and preserve regeneration guarantees with test coverage.

How do I test TypeScript generator changes to ensure regeneration contracts are preserved?

Implement changes to the TypeScript generator internals and run the generator test suite to verify that regeneration guarantees and predictable outputs remain intact.

Why does my TypeScript generator output change unpredictably after modifying OpenAPI schema handling?

Unpredictable output occurs when modifications to OpenAPI parsing or type coders break the deterministic output contract; changes must coordinate across the full Specification to Repository pipeline.

What should I avoid when modifying generated file writing behavior in a TypeScript generator?

Avoid changes that break deterministic output or bypass the regeneration contract, as downstream modifications must coordinate across Specification, coders, and repository writing with full test coverage.