Skip to content

Power steering files fail to load on detail page (Failed to load content for create-presentation.md) #157

Description

@zhutoutoutousan

Summary

On a Kiro Power detail page, the Steering Files tab lists the bundled markdown files but fails to render their contents. Expanding a file shows:

Failed to load content for create-presentation.md

The Prompt (POWER.md) and MCP Configuration tabs load correctly. The source steering files exist in the content library, so this looks like a website loading bug rather than missing content.

URL

https://www.promptz.dev/powers/promptz-power-create-powerpoint-slides

Screenshot

Image

Steps to Reproduce

  1. Open https://www.promptz.dev/powers/promptz-power-create-powerpoint-slides
  2. In Power Content, select the Steering Files tab
  3. Expand create-presentation.md (and optionally edit-presentation.md / visual-content.md)

Expected Behavior

Each steering file accordion should show the markdown from the power bundle, e.g. powers/create-powerpoint-slides/steering/create-presentation.md in promptz.lib.

Actual Behavior

The filenames are listed, but the expanded content is the error string:

Failed to load content for create-presentation.md

The other two files (edit-presentation.md, visual-content.md) are listed the same way and likely fail identically.

Environment

  • Site: promptz.dev (production)
  • Page: Create Powerpoint Slides
  • Author: rajikrishnamoorthy
  • Commit shown on page: c4319a1
  • Date shown: Feb 8, 2026
  • Browser: Chrome on Windows 10

Additional Context

This is a website issue per CONTRIBUTING.md (bug fix / website contribution), not a content PR against promptz.lib.

Source files on GitHub (all present):

The error copy matches the catch path in app/powers/[id]/page.tsx (loadSteeringFileContent), which reads steering files at request/render time with fs.promises.readFile after:

const powerDir = power.path.replace('/POWER.md', '')
const steeringFilePath = `${powerDir}/steering/${filename}`

Suggested Fix

Inline steering file contents into powers.json at build time (same pattern as content and mcpConfig), and render from that data instead of a runtime fs.readFile. Also resolve paths with path.join from the repo root rather than String.replace('/POWER.md', '').

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions