faasjs/faasjs · Archived

faasjs-specs

Use when implementing, reviewing, or verifying normative FaasJS runtime behavior and compatibility for faas.yaml, staged config discovery and merge order, zero-mapping route resolution, HTTP request/response protocol envelopes, status behavior, plugin identity, concurrent mount and failed-mount retry behavior, lifecycle execution, config layering, and config-driven plugin loading.

First seen Jun 23, 2026

Installation

$ npx skills add faasjs/faasjs --skill faasjs-specs

Summary

Use when implementing, reviewing, or verifying normative FaasJS runtime behavior and compatibility for faas.yaml, staged config discovery and merge order, zero-mapping route resolution, HTTP request/response protocol envelopes, status behavior, plugin identity, concurrent mount and failed-mount retry behavior, lifecycle execution, config layering, and config-driven plugin loading.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Also in this package

Other skills from faasjs/faasjs.

npx skills add faasjs/faasjs

Browse all from faasjs/faasjs

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 121
License LICENSE
Default branch main
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,774 B
  • docs SUMMARY.md 403 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 187 installs

SKILL.md

FaasJS Specifications

Default Workflow

  1. Load the relevant spec before changing runtime behavior or public documentation.
  2. Treat MUST/SHOULD/MAY language as normative.
  3. Keep implementation, docs, and tests aligned with the spec.
  4. Preserve backwards compatibility unless the change is intentionally breaking and documented.

Load These References

  • faas.yaml placement, discovery, merge order, staging keys, server node, plugins node, and YAML subset: references/specs/faas-yaml.md.
  • Zero-mapping file naming and route lookup order: references/specs/routing-mapping.md.
  • HTTP request, response envelope, status, and transport behavior: references/specs/http-protocol.md.
  • Plugin identity, lifecycle execution, config layering, manual registration, and config-driven loading: references/specs/plugin.md.

Gotchas

  • Specs are normative and may be stricter than general guides.
  • Route behavior and config merge order are compatibility-sensitive.
  • HTTP response behavior must preserve envelope and low-level error distinctions.
  • Plugin config precedence must stay aligned with both manual and config-driven loading.

Validation

  • Run targeted runtime tests for the spec area changed.
  • Run npm run doc after spec source edits.
  • Run cd docs && npm run build when docs routing, spec pages, or links change.