fraimz

Generate narrated proof artifacts from CDP and script-based user interactions.

3.2k|690|Updated Aug 25, 2025
One-click install
npx skills add https://github.com/Devin-AXIS/iPolloWork --skill fraimz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fraimz
Source: https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/fraimz
Command: npx skills add https://github.com/Devin-AXIS/iPolloWork --skill fraimz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The fraimz Skill provides a systematic approach to prove the functionality and quality of app experiences by generating detailed, narrated evidence of user interactions and system responses.

Core Features & Use Cases

  • Fraimz Generation: Automatically create a proof artifact (fraimz.html) capturing each step of user interaction, including screenshots, voiceovers, and system assertions.
  • User Experience Validation: Ensures that every feature, fix, or UX change is accompanied by verifiable evidence, improving trust and reducing post-launch issues.
  • Use Case: After deploying a new feature to production, use fraimz to create a proof artifact that includes screenshots, voiceovers, and system assertions demonstrating the feature's operation.

Quick Start

To create a fraimz for a flow, run the command: pnpm fraimz scaffold <flow-id>.

Frequently Asked Questions about fraimz

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create end-to-end proof artifacts for app experiences?

End-to-end proof artifacts for app experiences are generated by recording user interactions and system responses via CDP. This creates narrated HTML evidence, including screenshots and voiceovers, to verify complex feature workflows.

What is user experience validation and how does it work?

User experience validation ensures every feature or UX change is accompanied by verifiable evidence. It works by recording script-based user interactions and system assertions to capture narrated proof of functionality, reducing post-launch issues.

How do I generate narrated evidence for complex user journeys?

Narrated evidence for user journeys is generated by running a scaffold command to capture interaction steps. The tool utilizes CDP to record system responses, automatically producing an HTML artifact with screenshots and voiceovers.

Can I capture screenshots and system assertions without external dependencies?

Yes, you can capture screenshots and system assertions without external dependencies. The tool operates using internal scripts and CDP integration to independently record user interactions and generate the final proof artifact.

When do I need to generate proof artifacts for deployed features?

You need to generate proof artifacts for deployed features when you require verifiable evidence of functionality in production. This systematic proofing captures user journeys and system responses to build trust and reduce post-launch issues.

What's the best way to verify functionality after deploying a new feature?

The best way to verify functionality after deploying a feature is generating a comprehensive proof artifact. By recording script-based interactions through CDP, you capture screenshots, voiceovers, and system assertions demonstrating the feature's operation.