dollspace-gay

Verified Spec-Driven Development (VSDD)

The Fusion: VDD × TDD × SDD for AI-Native Engineering

Overview

Verified Spec-Driven Development (VSDD) is a unified software engineering methodology that fuses three proven paradigms into a single AI-orchestrated pipeline:

• Spec-Driven Development (SDD): Define the contract before writing a single line of implementation. Specs are the source of truth.
• Test-Driven Development (TDD): Tests are written before code. Red → Green → Refactor. No code exists without a failing test that demanded it.

steveruizok

{
	"hooks": {
		"PreToolUse": [
			{
				"matcher": "ExitPlanMode|Read|Write|Edit|NotebookEdit",
				"hooks": [
					{
						"type": "command",
						"command": "bash -c 'INPUT=$(cat); EVENT=$(echo \"$INPUT\" | grep -o '\"'\"'\"'hook_event_name'\"'\"'\"':[^\"]*\" | sed \"s/.*:\\(.*\\)/\\1/\" | tr -d '\"'\"'\"'\"); TRANSCRIPT_PATH=$(echo \"$INPUT\" | grep -o '\"'\"'\"'transcript_path'\"'\"'\"':[^\"]*\" | sed \"s/.*:\\(.*\\)/\\1/\" | tr -d '\"'\"'\"'\"); if [ \"$EVENT\" = \"Stop\" ] && [ -n \"$TRANSCRIPT_PATH\" ] && [ -f \"$TRANSCRIPT_PATH\" ]; then THINKING=$(tail -20 \"$TRANSCRIPT_PATH\" | grep '\"'\"'\"'type'\"'\"'\"':\"thinking\" | tail -1 | perl -ne \"print \\$1 if /\\\"thinking\\\":\\\"((?:[^\\\"\\\\\\\\]|\\\\\\\\.)*)\\\"/;\" | sed \"s/\\\\\\\\n/ /g\" | sed \"s/\\\\\\\\\\\"/\\\"/g\"); if [ -n \"$THINKING\" ]; then say -v \"Allison (Enhanced)\" -r 250 \"$THINKING\" & fi; fi; exit 0'"
					}

siliconjungle

import readline from 'readline'
import chalk from 'chalk'
import OpenAI from 'openai'
import { LocalIndex } from 'vectra'
import { fileURLToPath } from 'url'
import path, { dirname } from 'path'

const __filename = fileURLToPath(import.meta.url)
const __dirname = dirname(__filename)

Hellisotherpeople

You probably don't know how to do Prompt Engineering

(This post could also be titled "Features missing from most LLM front-ends that should exist")

Apologies for the snarky title, but there has been a huge amount of discussion around so called "Prompt Engineering" these past few months on all kinds of platforms. Much of it is coming from individuals who are peddling around an awful lot of "Prompting" and very little "Engineering".

Most of these discussions are little more than users finding that writing more creative and complicated prompts can help them solve a task that a more simple prompt was unable to help with. I claim this is not Prompt Engineering. This is not to say that crafting good prompts is not a difficult task, but it does not involve doing any kind of sophisticated modifications to general "template" of a prompt.

Others, who I think do deserve to call themselves "Prompt Engineers" (and an awful lot more than that), have been writing about and utilizing the rich new eco-system

aweary

import { z } from "zod";
import { zodToTs, printNode } from "zod-to-ts";
// Replace with your `openai` thing
import { openai } from "../openai.server";
import endent from "endent";


function createJSONCompletion<T extends z.ZodType>({
  prompt,
  schema_name,

kettanaito

Chromium on Vercel (serverless)

This is an up-to-date guide on running Chromium in Vercel serverless functions in 2022. What you will read below is the result of two days of research, debugging, 100+ failed deployments, and a little bit of stress.

Getting started

Step 1: Install dependencies

Use chrome-aws-lambda that comes with Chromium pre-configured to run in serverless, and puppeteer-core due to the smaller size of Chromium distributive.

geastwood

# ZSH
autoload -U add-zsh-hook

# place default node version under $HOME/.node-version
load-nvmrc() {
  DEFAULT_NODE_VERSION=`cat $HOME/.node-version`
  if [[ -f .nvmrc && -r .nvmrc ]]; then
    fnm use
  elif [[ `node -v` != $DEFAULT_NODE_VERSION ]]; then
    echo Reverting to node from "`node -v`" to "$DEFAULT_NODE_VERSION"

dethi

#!/bin/bash

# Launch inside a create-react-app project after building the production build.
# Require `jq`.

diff \
	<(find src -type f \( -name '*.js' -o -name '*.jsx' -o -name '*.css' \) | sort) \
	<(cat build/**/*.map | jq --raw-output '.sources | join("\n")' \
		| grep -v '\.\./' | grep -E '\.(js|jsx|css)$' \
		| sed "s#^#src/#" | sort | uniq) \

ryansimms

Deploying to Elastic Beanstalk via CircleCi 2.0

I got to here after spending hours trying to deploy to an Elastic Beanstalk instance via CircleCi 2.0 so I thought I'd write up what worked for me to hopefully help others. Shout out to RobertoSchneiders who's steps for getting it to work with CircleCi 1.0 were my starting point.

For the record, I'm not the most server-savvy of developers so there may be a better way of doing this.

Setup a user on AWS IAM to use for deployments

• Add user here

natedoesweb

export default (routes) => {
  return {
    fire (func,funcname, args){
      funcname = (funcname === undefined) ? 'init' : funcname;
      if (func !== '' && routes[func] && typeof routes[func][funcname] == 'function'){
        routes[func][funcname](args);
      }
    },
    load() {
      var bodyId = document.body.id;