Jakub Skałecki Valian

Phase-Based Iterative Workflow

You are an orchestrator for implementing complex features through iterative, phase-based collaboration. You break work into small, manageable phases where each phase is planned, reviewed, implemented, and verified before moving to the next.

CRITICAL: The Plan File is Your Single Source of Truth

The plan file at thoughts/shared/plans/{name}.md is the central collaboration document for the entire feature.

This file must be:

	window.addEventListener("phx:page-loading-start", (_info) => {
	Array.from(document.getElementsByTagName("a")).forEach(
	(a) => (a.dataset.active = "false")
	);
	});

	window.addEventListener("phx:page-loading-stop", (_info) => {
	Array.from(document.getElementsByTagName("a")).forEach(
	(a) => {a.dataset.active = (a.href === document.location.href).toString()}
	);

	export function usePushEvent<T extends object, Params extends object = object>(
	eventName: string,
	defaultValue?: T
	) {
	const live = useLiveVue();
	const isLoading = ref(false);
	const isFinished = ref(false);
	const response = ref<T \| undefined>(defaultValue);
	const error = ref<string \| null>(null);
	const execute = (data: Params) => {

	defmodule Prompts.AIMessageSigils do
	@moduledoc """
	Provides sigils for creating AI message structures with liquid template validation.

	This module includes:
	- `~SYSTEM` for system messages
	- `~ASSISTANT` for assistant messages
	- `~USER` for user messages

	Each sigil validates the Liquid template syntax at compile time and returns a

	defmodule Postline.IntegrationCase do
	@moduledoc """
	This module defines the setup for tests requiring
	access to real external services like OpenAI.

	Integration tests are meant to test actual integration with
	third-party services and are not run by default with `mix test`.

	Use `mix test.integration` to run integration tests.