PopNowAPI
Get API key

Junie skills

Install PopNow skills in Junie. Download a skill, unzip it into the skills folder, and call it by name in your next chat.

Browse 6 skills Junie documentation
  1. 1Copy the install prompt

    Paste it into Junie. It downloads the skill with your API key and unzips it into the right folder.

  2. 2Ask for the result

    Call the skill and say what you need in plain words: the topic, the audience, the length.

  3. 3Review and refine

    Open the file it made, ask for changes in the chat, and ship when it looks right.

All skills

  • Project Retrospective PresentationSlides

    Editable project retrospective presentation with checked inputs, evidence and speaker notes.

  • Case Study Website TemplateWeb

    An evidence-led case study page with baseline and outcome comparisons, missing-source warnings and a claim audit export.

  • UX Case Study PortfolioWeb

    Present design decisions with traceable evidence, clear ownership and honest outcome labels.

  • Case Study PresentationSlides

    Editable case study presentation with checked inputs, evidence and speaker notes.

  • Designer Portfolio WebsiteWeb

    Six tilted cards hover round a fading headline on calm grey, one red portrait card, editorial case studies.

  • Developer Portfolio WebsiteWeb

    A dark personal site for engineers with case studies, writing, talks, a résumé and a contact form.

Create a Junie project handoff that explains the work

Select the handoff for the reader

Junie users can give a project a clearer ending by preparing a design artifact that explains what changed and why it matters. Project Retrospective Presentation is suited to inspecting the sequence of work and follow-up actions. Case Study Website Template is a web direction to compare when the audience needs an independently readable account. UX Case Study Portfolio is another candidate when design reasoning is central. These suggestions organize supplied evidence; they do not establish outcomes on their own. Decide whether the handoff is for a project review meeting, a public case study or a portfolio reader.

Keep the Junie installation separate

PopNow records ~/.junie/skills for personal skills and .junie/skills for repository skills. Extract the full package, with SKILL.md and supporting assets together in the popnow-prefixed directory. Invoke it by its plain skill name and provide the project brief. Kiro uses its own .kiro folders, so a team that moves between those assistants should check the relevant installation card rather than assume shared instructions. When a handoff task produces generic prose, first confirm discovery; then examine whether enough project evidence was supplied to support a meaningful narrative.

Review the case study as an argument

For an initial Junie handoff, bring the original problem, constraints, approved screenshots, actual changes and records of the outcome. Separate observed effects from interpretations and future plans. Ask for a narrative outline before selecting a visual style. A retrospective should preserve chronological events and follow-up ownership; a portfolio piece should make the author's contribution clear without overstating it. Remove private details before turning internal work into a public example. If a rendered page fails, inspect dependencies and assets. If the story feels unconvincing, improve the evidence and explain the tradeoffs instead of adding more decorative sections to the artifact.

Three ways to install

Install guides by agent

Same skills everywhere; only the folder changes.

Frequently asked questions

Which Junie scope should I use for a project handoff?

Use .junie/skills when the workflow belongs to the repository, or ~/.junie/skills for your personal toolkit. Keep the complete package under that scope and use its plain name in the request. Supply project records separately from shared instructions, especially when those records include private information.

Should a retrospective become a public case study unchanged?

Not automatically. A retrospective serves an internal learning conversation, while a public case study needs authorized material and an understandable account for outsiders. Review confidentiality, evidence and attribution before adapting the work. Choose the skill format according to the reader rather than simply reusing the meeting slides.

What evidence belongs in a UX case study brief?

Provide the problem, constraints, design decisions and examples of the resulting interface. Identify your contribution and supply records for any claimed outcome. UX Case Study Portfolio is worth inspecting as a presentation format, but the credibility of the story depends on those source materials.

How do I fix a case study with weak conclusions?

Ask Junie to separate established observations from interpretation and identify unsupported statements. Add the missing records or narrow the claim. A clearer account of constraints and tradeoffs is more useful than a confident success narrative that cannot be traced back to evidence from the project.

Start building in minutes

One key for every model, a USD balance you top up when you need to, and an exact price before every run.

Get API key Try in Playground