Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

faasjs-specs

Estrelas120

Forks19

Atualizado17 de julho de 2026 às 09:20

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

faasjs

faasjs/faasjs

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

5 arquivos

SKILL.md

readonly

name	faasjs-specs
description	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.

FaasJS Specifications

Default Workflow

Load the relevant spec before changing runtime behavior or public documentation.
Treat MUST/SHOULD/MAY language as normative.
Keep implementation, docs, and tests aligned with the spec.
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.

Mais deste repositório

mesmo repositório

faasjs-api-jobs

faasjs/faasjs

Use when building or reviewing FaasJS backend APIs and jobs: .api.ts files, defineApi, zod params schemas, HttpError, HTTP helpers, middleware/staticHandler, .job.ts files, defineJob, typed job paths and params, enqueueJob including transaction-coupled enqueueing, cron schedulers, retries, leases, workers, discovery, and job tests.

2026-07-17120

faasjs-best-practices

faasjs/faasjs

Use when working in any FaasJS repo and no narrower FaasJS skill is already selected, or when a task spans project conventions, validation gates, security boundaries, and multiple FaasJS subsystems. For focused work, also load the relevant FaasJS skill: faasjs-project-workflow, faasjs-react-ant-design, faasjs-api-jobs, faasjs-pg, faasjs-plugins-runtime, faasjs-utils-data, or faasjs-specs.

2026-07-17120

faasjs-pg

faasjs/faasjs

Use when working with @faasjs/pg or PostgreSQL in FaasJS: Tables declaration merging, QueryBuilder, select aliases, parameterized sql expressions, raw SQL, numeric/decimal/bigint boundaries, transaction isolation and read-only modes, row locks, concurrency, migrations, SchemaBuilder, TableBuilder, faasjs-pg CLI, PgVitestPlugin, and database type tests.

2026-07-17120

faasjs-plugins-runtime

faasjs/faasjs

Use when building or reviewing FaasJS plugins and runtime infrastructure: Plugin lifecycle hooks including concurrent mount and failed-mount retry behavior, InvokeData mutation, DefineApiInject module augmentation, faas.yaml plugin loading, applyConfig, logger usage, @faasjs/node-utils, loadConfig, loadDotenv, module loaders, and Node-only bootstrap code.

2026-07-17120

faasjs-project-workflow

faasjs/faasjs

Use when creating, configuring, reviewing, or onboarding a FaasJS project; working with create-faas-app, vp CLI, TypeScript or Vite config, feature folders, file and naming conventions, test placement, JSDoc/comments, or complete application slice workflow.

2026-07-17120

faasjs-react-ant-design

faasjs/faasjs

Use when building or reviewing FaasJS React UI, especially @faasjs/ant-design pages, useFaas, useFaasStream, faas requests, CRUD screens, Table faasData, Description faasData, Form faas, conditional FormItem hidden/if behavior, drawers/modals, React hooks, shared state, and React tests.

2026-07-17120

name	faasjs-specs
description	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.

FaasJS Specifications

Default Workflow

Load the relevant spec before changing runtime behavior or public documentation.
Treat MUST/SHOULD/MAY language as normative.
Keep implementation, docs, and tests aligned with the spec.
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.