Prompting Is Maturing Into Design Infrastructure
Why this matters to Wen: once your best prompts become reusable skills, your design judgment stops living in scattered notes and starts behaving like a system.
Evidence: Figma is explicitly treating reusable plain-English instructions as shared team infrastructure, not as one-off prompt cleverness.
The Story
Figma's skills piece is a small story with a big implication. The interesting part is not that prompts can be saved. It is that teams are starting to externalise tacit judgment into reusable instructions that travel across projects and people. That changes prompting from a private productivity trick into a visible design asset.
There is real leverage in that shift. A strong critique prompt, naming convention, accessibility check, or handoff routine stops depending on memory and mood. It becomes a thing the team can refine, share, and rerun. That matters because so much good design work is still hidden in how someone frames a problem, not only in the final frame they produce.
For Studio Wensday, this is a clue about content too. Your best thinking around audits, editorial angles, and brand reviews can be turned into named methods. That gives you material for posts, a more consistent internal workflow, and proof that your taste is procedural rather than accidental.
Studio Wensday Angle
Choose one task you repeat often, such as critiquing a landing page or shaping a carousel concept. Write the exact instruction set you wish a good junior collaborator already knew, test it twice, then package it as a Studio Wensday method.