mcpField
F
faasjs-utils-data

faasjs-utils-data

github.com/faasjsDevelopment120187 installsUpdated 10w ago
Repository

About faasjs-utils-data

A FaasJS development skill for selecting and using data utilities, from JSON and YAML handling to validation and path checks. It also describes focused testing and handoff checks for utility changes.

Key features

  1. 01Guidance for choosing portable helpers
  2. 02JSON parsing and stream pairing
  3. 03YAML parsing and config loading
  4. 04Zod validation and type guards
  5. 05Root-scoped path containment checks
  6. 06Focused tests and code checks

Use cases

  1. 01Choosing a helper for a JSON or text payload
  2. 02Parsing YAML or staged FaasJS config
  3. 03Validating external data and unknown values
  4. 04Checking paths before Node-side file access

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/faasjs/faasjs --skill faasjs-utils-data

After installing, type/faasjs-utils-datain Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/guidelines/
json.md
utils.md
valid.md
yaml.md

Details

From the project README

FaasJS Utils And Data

Default Workflow

  1. Use the smallest helper that matches the payload shape.
  2. Keep JSON helpers paired with JSON payloads and text helpers paired with text streams.
  3. Use Zod schemas for external data validation and helper type guards for unknown internal values.
  4. Use parseYaml() for direct YAML parsing; use loadConfig() when staged FaasJS config discovery is required.
  5. Validate root-scoped paths before file access in Node-side tooling.

Load These References

  • Portable helpers and quick selection rules: references/guidelines/utils.md.
  • JSON parsing and JSON stream helpers: references/guidelines/json.md.
  • Direct YAML parsing: references/guidelines/yaml.md.
  • Zod helpers, object narrowing, schema parsing, and path containment: references/guidelines/valid.md.

Gotchas

  • Do not replace internal control-flow checks with Zod schemas.
  • objectToStream pairs with streamToObject; stringToStream pairs with streamToString.
  • Use loadConfig() instead of direct YAML parsing when config staging and merge order matter.

Validation

  • Run focused unit tests with vp test <pattern> for helper behavior changes.
  • Run vp check --fix before handoff when utility files changed.

Comments

Markdown supported