Product and tools
Rise Code Block Skill
A Claude Skill that builds custom Rise 360 interactions that are accessible, on brand and editable by authors who do not code.
- Built for the Rise Code block sandbox
- Author-editable CONFIG in every block
- Saved brand profiles
- Checked at phone and desktop widths
- Role
- Product Design and Innovation Lead
- With
- Foundation Education
- When
- 2026
- Practice
- Products and tools, Interaction design, Learning design
Project
A Claude Skill that builds custom interactions for Rise 360
At Foundation Education I design and build new interactions for Articulate Rise 360 using its Code block, to create more engaging learner experiences than the native block library allows. To make that repeatable, I wrote a Claude Skill: a packaged set of instructions, reference files and worked examples that teaches Claude how to build an interaction that is correct for Rise, accessible, on brand and editable by a colleague who does not code.
The problem
Rise's block library is fast to author with, but it is a fixed menu. When the learning calls for something else, such as a risk matrix a learner can explore, an animated exercise demonstration or a fill-in activity card, the Code block is the only route. It accepts a single HTML file and runs it in a sandbox, and that sandbox has rules that ordinary web code does not expect:
- It is isolated. The block inherits none of the course's theme or fonts, so anything not rebuilt inside it looks like it came from somewhere else.
- Rise controls the height. Full-height layouts measure the sandbox, not the lesson, and get clipped.
- Completion is a message. The block only counts as complete if it tells Rise so, once, at the right moment.
- Downloads, print dialogs and alerts are blocked, and browser storage is unreliable.
- Rise's accessibility stops at the frame. Everything inside has to stand on its own for keyboard and screen reader users.
An AI model asked for "a flip card interaction" will write clean, attractive code that ignores all of this. The result is white boxes on dark courses, clipped content and no completion tracking. Fixing each block by hand, and re-explaining the same rules in every conversation, does not scale to whole units of content.
The solution
The skill does not replace the model's judgement about good interaction design. It adds the knowledge specific to Rise and to our organisation, in layers:
- The Rise contract. Five requirements for transparent backgrounds, auto-resize, guarded completion, in-memory state and self-contained theming, each with the reason it exists.
- An editable CONFIG block. Every value a non-coder might change (wording, colours, fonts, heading level, the completion setting) sits in one plainly commented section at the top of the file, so an instructional designer can update a block without touching the logic.
- A brand library. Saved brand profiles hold tested colours, fonts and shapes, with the contrast traps written down, such as which text colour is readable on each brand colour. A brand is applied only when asked for.
- UX writing rules. Instructions follow one pattern, so the same interaction gets the same wording in every block of every unit. Buttons have two clear roles, navigation and in-screen actions, and never share a label.
- Accessibility built in. Keyboard operation, visible focus, live regions, reduced-motion support, touch target sizes and contrast checks are part of the definition of done.
- Design principles from review. Guidance on letting colour carry meaning, choosing a layout from the logic of the content, and showing one item at a time inside a metaphor tied to the topic.
- A pitfalls list. Dozens of real failures, each recorded with its cause and its fix, so the same mistake is not made twice.
- A pre-delivery check. Each block is loaded in a test page that copies Rise's sandbox settings and checked at phone and desktop widths for overflow, console errors and exactly one completion message.
My role
I designed, wrote and maintain the skill:
- Investigating the platform: Working out how the Code block renders, what its sandbox allows and how it interacts with course theming, including themes applied by my Rise custom styling extension.
- Setting the standards: Defining the layout, heading, button, feedback and completion conventions, and aligning the instruction wording to our UX writing style guide.
- Building the brand profiles: Distilling each brand's Rise theme and style guide into tokens a self-contained block can use, and verifying the contrast of every pairing.
- Reviewing and iterating: Reviewing every generated block as a learning designer, then turning each piece of feedback into a rule or a recorded pitfall so the improvement carries forward.
- Art direction: Directing a reusable illustrated character and anatomy kit so every figure in a unit shares one body, one style and one set of proportions.
Process
1. Learn the contract
The first version captured what makes a block work in Rise: the sandbox permissions, the resize behaviour and the completion message. In automated checks it scored far higher than building with no skill at all. Then I compared the actual outputs, and the blocks built without the skill were more functional and better looking. The skill had taught compliance at the cost of quality.
I had it rewritten around that finding. Its opening instruction now sets the tone for everything after it: build the best interaction you can, then make it correct for Rise. Passing the rules while looking or working worse than a plain build counts as a failure.
2. Make blocks editable by authors
Rise gives no way to edit a Code block through its normal interface, so a block that only its builder can change becomes a maintenance problem. The CONFIG pattern was the answer: content first, then heading level, brand and behaviour, numbered the same way in every block, with a short plain-English comment on every value.
3. Teach it the house style
I added the conventions that keep a whole unit consistent: a default width that suits a Rise lesson, no headings above the level the lesson allows, instructions placed directly before the control they describe, and one completion pattern used everywhere. Knowledge checks support the learner to reach the right answer instead of counting attempts.
4. Add brands without making them a cage
Brand profiles came next. Reviewing the first branded blocks showed that rigid branding communicated worse than thoughtful branding. The blocks that worked best kept the brand in the fonts, shapes and buttons, and let the subject's own colour language carry the content: safety-sign colours, traffic lights for levels of risk, exit green for evacuation. That became a written principle, with the rule that meaningful colour beats brand colour.
5. Turn every review into a rule
Each round of feedback on real blocks was folded back into the skill. A flip card that showed both faces, an uneven number of cards left as orphans in a grid, a popup that opened in the middle of a tall block and far from the learner on a phone: each became a named pitfall with its cause and fix. The skill improves every time it is used.
6. Illustration and animation
Fitness units need the body drawn accurately: labelled anatomy, joint models and animated exercise demonstrations. I directed a reusable base character with a consistent skeleton and layers, plus rules that put anatomical accuracy first. Poses are checked against the coaching cues in the text, joints are tested so they never bend the wrong way mid-animation, and each loop is reviewed as a sheet of frames instead of a single screenshot.
7. Activities that leave the screen
The sandbox blocks downloads and print dialogs, so fill-in activities open a clean printable copy in a new browser tab, with saving steps for computer, iPhone and Android. Blank fields print as ruled lines, so the same card works for learners who prefer to write by hand.
Impact
Impact and outcomes
- Beyond the block library. Learner guide tables and lists become interactions designed for the learning goal, such as comparing, predicting, uncovering, ordering and applying, instead of whatever the native blocks happen to offer.
- Consistent across a suite. Every block follows the same layout, wording, button and completion conventions, so a learner meets the same patterns from unit to unit.
- Accessible and responsive by default. Keyboard operation, contrast, reduced motion and phone layouts are checked on every block, not added afterwards.
- Maintainable by the team. Colleagues can change wording, colours and behaviour in the CONFIG section without a developer.
- On brand in one request. A saved brand profile restyles a block while keeping its mechanics and accessibility intact.
- Knowledge that compounds. Review feedback is captured once and applied to every block built afterwards.
This sits alongside my work designing GUIs and branded assets for digital learning products, all WCAG compliant with responsive scaling across devices.