Results for “phase-based”

Design, select, and analyze waveforms for radar, sonar, and active sensing using the Phased Array System Toolbox. Covers LFM, NLFM, FMCW, phase-coded, CW, stepped FM, custom IQ, ambiguity functions, sidelobe reduction, and Doppler tolerance. Key objects: phased.LinearFMWaveform, phased.NonlinearFMWaveform, phased.CustomFMWaveform, phased.PhaseCodedWaveform, phased.FMCWWaveform, phased.SteppedFMWaveform, phased.MFSKWaveform, phased.RectangularWaveform, nlfmspec2freq, shapespectrum, ambgfun, pambgfun, sidelobelevel, legendreseq, mlseq, radarWaveformGenerator.

Runs a complete quality engineering audit on any codebase, deriving behavioral requirements, generating spec-traced tests, performing multi-pass code review, and producing a consolidated bug report with verified patches.

Build web-based games and game engines using HTML5 Canvas, WebGL, and JavaScript with frameworks like Phaser, Three.js, and Babylon.js.

Creates a machine-readable phased JSON plan bundle from a spec or feature description, producing a compact master manifest plus per-phase step files for resumable execution.

Creates a machine-readable phased JSON plan bundle from a spec or feature description, producing a compact master manifest plus per-phase step files for resumable execution.

4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.

Create and manage stacked (dependent) pull requests for complex features

Batch Signal Isolation with Recipe-Driven Processing

Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.

Tracks crypto and AI narratives with mindshare scores, velocity arrows, phase labels, named drivers, and position calls. Detects phase transitions and reflexivity signals.

当感到生活迷茫、停滞不前，需要理解当前所处阶段并规划下一步行动时

State-Based Button Display Skill

Implements a feature phase by phase from a phased JSON or Markdown plan, with configurable unit-test and quality-gate choices per phase, token-budgeted execution, resumable state, and TDD handoff.

Splits a body of context into a sequence of vertical-slice build phases where each phase is independently demonstrable to a real user and each builds on the previous. Use when the user wants to plan, sequence, phase, slice, break down, or order the build of a feature, capability, system, or initiative, and produces a plain-language phased build outline. Does not produce implementation detail — use plan-implementation. Does not specify behavior that has not been decided — use plan-a-feature. Does not perform gap analysis between two artifacts — use gap-analysis. Does not break a plan into independently-grabbable work items — use plan-work-items.

Guides the red-green-refactor cycle for implementing features with test-driven development, including test quality guidelines, framework setup, and commit patterns.

Procedurally design an AAA-style open-world FPS map blockout (roads, POIs, fields, forests/treelines, railway/bridges) from a landscape, validate it through gated checks, and materialize it into engine geometry. Use when the user asks to block out or lay out an open-world/FPS map, place roads/POIs/forests/railways procedurally, or turn a blockout plan into splines, paint layers, foliage, and actors.