Agent skill · software engineering · jeremylongshore
framer-ci-integration
Configure Framer CI/CD integration with GitHub Actions and testing.
Why this skill is useful
Adds a complete CI/CD integration script for Framer with GitHub Actions, including automated testing and CMS synchronization that the AI cannot generate on its own.
What it needs
Requires node installed locally. Requires github account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Framer CI Integration Prerequisites Protected CI environments, scoped credentials available only to trusted jobs, synthetic site/CMS fixtures, and a deployment owner. Error Handling Stop promotion on failed build, publish, domain, integration, or privacy checks; roll back the canary and preserve redacted evidence for review. Examples Run fixture-based tests with no secrets on a pull request, then use a protected staging job to publish a fictional canary. Block production promotion when a route, integration, or access check differs from the approved result. Overview Set up CI/CD for Framer plugins and Server API integrations. Plugin builds are tested with Vite + vitest. Server API CMS sync can be triggered from CI for automated content publishing. Instructions Step 1: GitHub Actions for Plugin Build Step 2: CMS Sync Script for CI Step 3: Configure Secrets Output Plugin builds verified on every PR Automated CMS sync and publish on main push Secrets configured in GitHub Resources GitHub Actions Framer Server API Next Steps For deployment, see framer-deploy-integration.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/framer-ci-integration