Skip to content

Add fastly-reference-architectures skill - #13

Merged
jedisct1 merged 17 commits into
fastly:mainfrom
aspires:fastly-reference-architectures
Aug 26, 2026
Merged

jedisct1 merged 17 commits into
fastly:mainfrom
aspires:fastly-reference-architectures

Conversation

@aspires

@aspires aspires commented Aug 20, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Adds a new fastly-reference-architectures skill: curated GitHub repos demonstrating working reference architectures on Fastly, from single Compute apps up through systems combining multiple Fastly products.
  • Five reference files split by architecture concern (edge auth/security, caching/delivery, compute application patterns, multi-service architectures, observability/ops), each with a handful of vetted entries and a documented freshness self-check mechanism for agents recommending an entry.
  • Lists the new skill in the root README.

Test plan

  • markdownlint-cli@0.47.0 passed against all new/changed files (confirmed via a cached binary during final review; the author's local environment had a persistent TLS issue blocking a live npm install)
  • SKILL.md frontmatter (name-matches-folder, description present) and duplicate-skill-name checks passed, run manually against all 10 skills in the repo
  • Content review: every entry checked for accuracy against its source repo (not just its GitHub description), no invented facts, governance/endorsement bar documented
  • skillscheck --strict — please confirm this passes in CI on this PR; the author's environment could not run it directly (network-restricted sandbox)

🤖 Generated with Claude Code

aspires and others added 14 commits August 19, 2026 12:05
…ples

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…MD001)

All entry headings in edge-auth-and-security.md changed from H3 (###) to H2
(##) to fix markdownlint MD001 violation (heading-increment). Updated the
schema template in SKILL.md to match the corrected convention.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… examples

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…caveat, not editorial note

Replace the editorial instruction in the edge-mcp entry's Watch out for field
with the actual maintenance caveat from the repository: point-in-time example
built against MCP 2026-07-28, will not be maintained beyond initial implementation.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…examples

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ers entry

The fastly-serverless-checkers entry's Demonstrates field now explicitly
names all three products (Compute, Fanout, KV Store) instead of implying
Compute through "no backend servers."

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- Add fastly-ngwaf to SKILL.md's "Not this skill" list, which omitted it
- Remove stray blank lines after entry headings in caching-and-delivery.md
  so all five reference files use consistent formatting
…accuracy, coverage claims, naming consistency

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Keeps brainstorming specs and implementation plans as local scratch
artifacts rather than tracked repo content.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@jedisct1

Copy link
Copy Markdown
Collaborator

This is way too verbose.

SKILLs are instructions for machines, not documentation for humans, so they don't need prose, fancy formatting, explanations of things even a small model already knows, etc.

In the main index, we could simply have an Example projects running on Fastly (git repositories) link to a document containing a table like this:

Project Description Platform
plot-for-fastly Plot JSON data as histograms Compute
secureheaders Add security headeres VCL

…ove liveness check to CI

Per review feedback from jedisct1: skills are machine instructions, not
human docs, so drop the prose and the 5-field-per-entry schema in favor
of one compact table (project/description/platform) linked from
SKILL.md. Also drop the agent-side "check the repo isn't archived
before recommending it" instruction — that cost belongs in CI, not on
every recommendation, so a new check-example-repos job now verifies
each linked repo is live and unarchived on every push/PR.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@aspires

aspires commented Aug 20, 2026

Copy link
Copy Markdown
Member Author

This most recent commit should address the feedback, thanks again @jedisct1

Comment thread .gitignore Resolved
Comment thread .github/workflows/skillscheck.yml Resolved
aspires and others added 2 commits August 20, 2026 15:13
…rop unrelated gitignore change

- Drop SKILL.md's "add/remove via PR, CI checks liveness" line — not
  useful to the skill's consumer, only to maintainers.
- Move check-example-repos into its own workflow file; it has nothing
  to do with the skillscheck command skillscheck.yml is named for.
- Revert the docs/superpowers/ .gitignore entry — unrelated to this
  skill and out of scope for this PR. Kept as a local-only exclusion
  in .git/info/exclude instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
CI's check-example-repos job caught this: the repo's visibility
changed from public to internal since it was curated, so the
workflow's repo-scoped token (correctly) can't see it. Not
appropriate as a public example if it's not publicly reachable.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@aspires

aspires commented Aug 20, 2026

Copy link
Copy Markdown
Member Author

Moving the repo status checks to CI already proved valuable. A repo was pulled from access in between creating the initial draft and the most recent commit.

@jedisct1

Copy link
Copy Markdown
Collaborator

@jedisct1
jedisct1 merged commit f7764e3 into fastly:main Aug 26, 2026
3 checks passed
jedisct1 added a commit that referenced this pull request Aug 31, 2026
Add fastly-reference-architectures skill
jedisct1 added a commit that referenced this pull request Sep 30, 2026
Add fastly-reference-architectures skill
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants